2.6.24 - time to switch

Andy Green andy at openmoko.com
Fri Feb 1 11:19:03 CET 2008

Hash: SHA1

Somebody in the thread at some point said:
> Hi Mickey,
> I think it's time to face down our fears and finally switch our
> principal tree from to 2.6.24.


> Now, I thought a bit about how we can bring the great change about
> in SVN, and since this is the first time I get to do this, I'd
> appreciate some advice. As far as I can tell, there are two options:

I don't have an opinion about that question but I do about a bit further
down the line.

What I would like to start doing before long -- if it isn't going to
kill me (or you) -- is start shadowing your svn commits in a new git
branch that maintains full history, patch log notes and so on in normal
git style.  I would like to replace mokopatches with that but in fact
since we start late in the game it would have to be a branch on top of a
"frozen mokopatches".

If it all turns to poop while we are trying this method out, I can
always rebase on your current mokopatches and try again with the
tracking.  But what I am hoping is it will work out fairly easily if I
am definitely getting the exact patches committed somehow.  I thought I
could do it off the kernel list, but you are not posting your patches to
the list at all currently.  I don't want to do it by diffing the
mokopatch lumps because then I lost the attribution and commit log (I
really hate that about mokopatches).

So my question is, how can this integrate with what you are doing with
svn without agonizing pain or death (or losing attribution and commit
log of individual patches).

- -Andy
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the distro-devel mailing list