Even though I have yet to try this.. Which I'll do later tonight when I get home.. It's possible with subversion 1.7 to just use the svnrdump command to dump out a subtree from svn with history. Then to load it back up to to Github through their subversion interface. Thereby preserving all history, including branches if you follow the trunk/branches naming or manually load back into trunk and branches individually. I'll post some steps later tonight as to how the results look like. On Wed, Dec 12, 2012 at 4:06 PM, Mika Fischer <mika.fischer@zoopnet.de>wrote:
On Wed, Dec 12, 2012 at 9:57 PM, Beman Dawes <bdawes@acm.org> wrote:
git svn clone https://svn.boost.org/svn/boost/sandbox/endian [...] Comments? Is there a better way to do this?
This approach has the following disadvantages (which might or might not be important to you): - it will add git-svn-id lines to all commit messages - the commit authors will have invalid email addresses - their names will be the username in the svn repository
In case some or all of these issues bother you, I've successfully used the following instructions to create repositories that pretty much look like regular git repositories: http://stackoverflow.com/a/3972103/92542
Basically, for the first issue, you can pass "--no-metadata" to "git svn clone". And for the other issues you can provide a mapping from svn user to git user in a text file and pass it to "git svn clone" via "-A".
Best, Mika
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo