[cap-talk] Choice of version control: s/svn/git/ (was Re: Polaris distribution is ready)
Jonathan S. Shapiro
shap at eros-os.org
Tue Apr 27 10:53:28 PDT 2010
Definitely Git or Mercurial. The days of SVN are (and should be) over.
On Tue, Apr 27, 2010 at 10:31 AM, Kevin Reid <kpreid at switchb.org> wrote:
> On Apr 27, 2010, at 13:06, Mark Miller wrote:
> > I also notice CVS directories all over. Is there a CVS repository
> > with the history? Do you wish to open source that history as well?
> > I've heard there are CVS to SVN converters.
> > Would you be happy with a code.google.com project?
> FWIW, I no longer favor Subversion as the choice for version control.
> DVCS in general is simply better: there is no central point of failure
> (everyone automatically is a backup), there is no inherent need for an
> ACL for committers, and branching/merging support is (necessarily)
> In particular, handling merges in Subversion is tedious and/or hairy
> -- which discourages the use of branches, which discourages publishing
> less-than-perfect work, which reduces the rate of progress and
> developer interaction.
> I currently favor Git which, while the (default) user interface may be
> slightly unintuitive, has a very solid core semantics (which even
> makes sense from a capability perspective), and is effective and fast
> in my experience.
> Kevin Reid <http://switchb.org/kpreid/>
> cap-talk mailing list
> cap-talk at mail.eros-os.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cap-talk