I can see this descending into a mercurial vs git religious war :)<br><br>Hi Corey. I'm using mercurial for both home and work use (supplementing some of subversion's shortcomings, mainly around merging). I looked (briefly) at git and - less briefly - at darcs. I settled on mercurial for purely non-scientific reasons. People whose opinions I respect are using it, the community seems both accommodating and active, and it's python which means it runs anywhere python lives, which is all of my home and work environments.<br>
<br>Others on this list - including the lovely David - are using git and having just as much fun and productivity, so I'm sure it comes down to a matter of taste in the end.<br><br>The big shift, though, is from centralised to distributed source control. This means that any working copy is also a full repository in its own right, so you can do everything you would usually need the server for: branching, tagging, cloning, logging, checking in, rolling back, etc. This page (<a href="http://tinyurl.com/ykcs25">http://tinyurl.com/ykcs25</a>) from the Mercurial wiki gives a pretty good overview. The basic model will be the same for any of the distributed SCMs.<br>
<br>My experience so far is:<br><br><span style="font-weight: bold;">git</span>: insanely fast, made up of many shell scripts, big command set, does /BIG/ repositories (currently used for the entire linux kernel), doesn't run on windows.<br>
<span style="font-weight: bold;">darcs</span>: also fast, written in haskell so less "hackable". Has best cherry-picking support (choosing out-of-sequence changesets). Apparently doesn't do so well under biiig repositories.<br>
<span style="font-weight: bold;">mercurial</span>: also fast (seeing a pattern here?). Seems to scale well. Has (deliberately) svn/cvs-like command set where it can, so easy to adopt. This is where I've ended up.<br><span style="font-weight: bold;">monotone</span>: the first distributed scm I came across (Dave Astels was using it before any of the rest of us had heard of distributed scm). Never really used it much.<br>
<br>At the end of the day it will be a personal preference. But whichever you end up with, my prediction is that you'll enjoy it much more than subversion.<br><br>Cheers,<br>Dan<br><br><br><div><span class="gmail_quote">On 27/01/2008, <b class="gmail_sendername">Corey Haines</b> <<a href="mailto:coreyhaines@gmail.com">coreyhaines@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi, all,<br><br>This isn't about rspec, but this list has people whose opinions I respect.<br><br>So, I'm looking for a new version control system for my local development. I was going to install subversion, but I've heard rumors of people using some newer ones. Thoughts? I'd like to be able to run it either locally or on a home server. If I run it off a home server, then it needs to support offline access, so that I can use a cached version when I'm not on my home network. For simplicity's sake, running it locally is probably a better solution.<br>
<br>What do you all use?<br><br><br>-Corey<br clear="all"><span class="sg"><br>-- <br><a href="http://www.coreyhaines.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://www.coreyhaines.com</a><br>
The Internet's Premiere source of information about Corey Haines
</span><br>_______________________________________________<br>rspec-users mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:rspec-users@rubyforge.org">rspec-users@rubyforge.org</a><br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://rubyforge.org/mailman/listinfo/rspec-users" target="_blank">http://rubyforge.org/mailman/listinfo/rspec-users</a><br></blockquote></div><br>