Kevin Norton <[email protected]> writes: > i'm in the process of coming up with a strategy to convert a very large > project from SVN to GIT. > > i'm experimented with git svn clone but have some questions. > > how large is to large. > > current SVN repo > 80K+ revisions. > suffers from poor SCM practices > current structure in SVN is using cascading hierarchy. Essentially each > release branch becomes the trunk (not officially named as trunk) and then > next release branches to start next development release branch and so on, > Think of a stairway. > Essentially current code sitting in Trunk is extremely old, relevant code > is at the end of the branching staircase. > > My first issue i'm trying to sort out. > Should i migrate the entire SVN repo into a staging GIT repo and then clean > up the GIT repo before pushing to eventual network repo for all developers. > Will it even clone at this size? > Or i could clone only the latest release branch and start this as my Master > in GIT. > Questions with this approach are how do i keep it from walking the branches > back through entire SVN repo? > Only way I've seen so far is to specify SVN revision. Is there another > approach i'm overlooking. > Advantage here is smaller conversion but i'm loosing history or have to > maintain a legacy SVN repo for historical. (maybe its not important?) > > any experience or suggestions with the above are appreciated.
It's worth taking a look at https://subgit.com/ to see if that tool can simplify the conversion. It's proprietary, but the licensing is reasonable (https://subgit.com/pricing.html). /M -- Magnus Therning OpenPGP: 0x927912051716CE39 email: [email protected] jabber: [email protected] twitter: magthe http://therning.org/magnus Never be afraid to try something new. Remember, amateurs built the ark; professionals built the Titanic. — Anonymous -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
