Thanks Nando, I have attempted clone of entire repo. Basically i believe it will complete most likely afer a few days of restarts after failures. But most likely i need to take this opportunity to trim my repo and only clone what is necessary.
Old versions of code are most likely not valuable and this is a good opportunity to take a fresh start. My goal is to introduce better SCM practices, so the cleaner the repo, most likely the better chance of success. . On Thursday, November 3, 2016 at 12:11:34 AM UTC-7, Ferdinando Santacroce wrote: > > Hi Kevin. > > Il giorno mercoledì 2 novembre 2016 19:48:58 UTC+1, Kevin Norton ha > scritto: >> >> 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? >> > > I converted some SVN repo before, but no so big stuff (about 1k revisions). > Have you tried to run the git svn clone command just to see what happens? > It will take hours (please use powerful machine and reliable network), but > I think there's no better way to figure out if it will work. > > >> Or i could clone only the latest release branch and start this as my >> Master in GIT. >> > > This can be a way to set a "cut-line" and start with a new repo and a > better versioning strategy and flow. > > >> 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. >> > > Take a look at --ignore-paths option (https://git-scm.com/docs/git-svn); > you can use Perl regex to restrict the field of your clone command. > > >> Advantage here is smaller conversion but i'm loosing history or have to >> maintain a legacy SVN repo for historical. (maybe its not important?) >> > > Try to do a little retrospective: how much times do you look for old > commits and branches in you actual SVN repo? > Do an year or later old branch has some value for you today? > Or it is only a matter of historical purpose? > I you realize you never look at oldest branches, then I think you can > freeze the actual SVN repo (or convert it to Git but leave it apart) and > then start with a new Git repo with the latest 2-3 branches only. > > >> any experience or suggestions with the above are appreciated. >> > > Software evolves, and long-living repos often are just an heavy load to > drag than a real value. > Starting with a new tool can also be a chance to review your flow a choose > a better strategy (see GiFlow, GitHub flow, GitLab flow, etc.). > If I were in your shoes, I will take this chance and start with a new > smaller repo wit only the latest 2 branches/versions of the software. > > My 2 cents :) > Nando > -- 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 git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
