procedure for migrating to git, patch ingress policy, actual main issue

Andy Green andy at openmoko.com
Tue Mar 11 15:10:11 CET 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
> Andy Green wrote:
>> You seem to have elided a bit from how we left it in .tw, which involved
>> explicit migration to git during your holiday and someone shadowing it
>> in svn.
> 
> That's not quite what I remember, since this would mean that the
> migration would happen before we actually have a method that allows
> us to continue to synthesize sequential patches, thus possibly
> creating a rift in the code base.
> 
> Of course, if we can find a suitable solution for this earlier, then
> there's no reason to delay the migration. (Or, in fact, to continue
> maintaining the then completely redundant SVN repository.)

Since events today, the way forward involves Felipe tackling the
mokopatches in git and us working with and on top of the outcome of
that.  That's more of a plan than we had thismorning in terms of
upstream or transition to git.

As soon as Felipe starts on refactoring mokopatches, mokopatches are
deprecated as a development path, we should not add anything to them any
more but start collecting atomic patches in git on top of Felipe's new tree.

I'm more encouraged than I have ever been since I learned about
Mokopatches that someone is going to grasp the nettle that seems to have
eluded us for the whole project, and that we are going to have some real
progress in the development process.

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

iD8DBQFH1pLDOjLpvpq7dMoRAgLpAJ950t+ZMez5mKpG6usT05uUeIDriACfX2ua
h4Ro2wOyHLs+uAlXUWtA3X0=
=QZcB
-----END PGP SIGNATURE-----




More information about the openmoko-kernel mailing list