<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 11, 2013 at 10:50 AM, Tom Zeller <span dir="ltr"><<a href="mailto:tzeller@dragonacea.biz" target="_blank">tzeller@dragonacea.biz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">> Sorry to butt in, but if you're going to undergo a huge repo reorg why not<br>
> also take the opportunity to move to Git at the same time. Seems that was<br>
> desired by some (move to Git) in the past and the amount of work require to<br>
> pop a massive svn repo into several smaller git repos while preserving<br>
> history is really not all that much. I only mention this because we're<br>
> doing the same thing here in the IAM group at Chicago -- busting one massive<br>
> repo (ours in this case stretches back to 1999 and has gone through RCS -><br>
> CVS -> SVN -> Hg and now into smaller project-based git repos).<br>
</div><div class="im">>> import it into a fresh repo.<br>
<br>
</div>It would be great if people who have moved from svn to git could rough<br>
estimate the time and effort involved. My guess is that we would lose<br>
1 to 3 months worth of time on the learning curve. I still have alot<br>
to figure out with the actual deliverable.<br></blockquote><div><br></div><div>We didn't do SVN -> Git, we did SVN -> Hg, but the principal is the same. Converting our repository took maybe half-a-day to figure out the right options to pass to the conversion tools to make the resulting repo look the way we wanted it to. The learning curve was not as bad as you make it out to be. There are many guides and books out there which handle the topic of git for subversion users. In general, svn commit becomes git push. As DVCS are primarily designed with branch/merge being a common operation we find that, in general, merging into the master rarely needs manual conflict resolution. I think I've only really had to do manual cleanup twice in the last 4 years. Sure, you can get fancy with local branches, rebasing, cherry-picking, stashing, etc, but most of the time folks just wind up doing a commit && push & get the same effect as doing an svn commit.</div>
<div><br></div><div>Dave</div></div><br clear="all"><div><br></div>-- <br>David Langenberg<div>Identity & Access Management</div><div>The University of Chicago</div>
</div></div>