Hi Barry, thanks for this write-up.
An open question remains what to do about the current history that is in svn. My experience of doing this is as follows: * For many repos, svn-all-fast-export does an excellent job of turning a complete svn history into something that looks identical to what git- buildpackage would have made on its own. * For some repos, (especially when there were missing tags) svn-all-fast- export requires some additional grafts to be added and then the git history reworked. Of course, any conversion utility would require this -- it depends how ideally accurate you want your history to be, and given that the current history in svn can be incorrect, being overly picky is perhaps unwise. * And then for some repos, the conversion with svn-all-fast-export is an utter trainwreck and I was not able to work out why. (I did quite a lot of poking around and was unable to determined whether it was because I was using a newer svn than on previous conversions or because retagging had happened in that repo). I eventually gave up and used git-import-dscs -- debsnap. That said -- all the above experience was with full-source svn repos. I would anticipate that the debian/-only repos would be easier to migrate as they are much simpler, but then the new git repo would also be debian/-only. A minor git dance to import the next upstream source would be needed. I've not even contemplated how you'd go about adding historical upstream sources to the git repo. cheers Stuart -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ltjdto$aft$1...@ger.gmane.org
