-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
> Hmm, it would be good if you could find a way to already integrate > the SVN history into git. That's something we would need before we > can make a switch, so if it's not too painful to figure out how > this could be done now, why not start with a fully featured tree ? Hum apparently this isn't as scary as it sounds, last time it came up I googled around and indeed there are ways to automate it. And it's true if it can be done without shortening my lifespan significantly -- or making my hair fall out ;-) -- then it'll actually be pretty neat. >> I thought I >> could do it off the kernel list, but you are not posting your patches to >> the list at all currently. > > Every change to SVN automatically shows up in the commitlog. This is > infinitely more reliable than picking manual submissions from the > list (which may get some editing anyway). So I think that's the one > you want to use. Maybe I have the wrong end of the stick, but mokopatch blobs seem to be the "tree" in svn. If there's a way to get one-for-one the patches as patches that you applied out of svn (sort of peeling them off the mokopatch blobs), with attribution and Signed-off-by and log info intact, let me know and I will start meddling from that end. If we can get that working reliably it'll actually save me time overall since I have to fiddle about daily tracking the mokopatches by hand in git anyway. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHoxDLOjLpvpq7dMoRAiBYAKCLtP/FFkgbJIIOdbq1xhZ9XXQLigCdHmy/ H9Vd7jpcsEXPl/auEJpDABg= =KNnL -----END PGP SIGNATURE-----
