all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eric S. Raymond" <esr@snark.thyrsus.com>
To: emacs-devel@gnu.org
Subject: It's not yet time to anoint git, or anything else
Date: Wed,  2 Jan 2008 08:24:58 -0500 (EST)	[thread overview]
Message-ID: <20080102132458.387D9830B03@snark.thyrsus.com> (raw)

I'm glad there is active discussion of distributed VCSes happening 
on the list, as I strongly believe we should move to one in the 
near future.  

But I think it's worth noting that pretty much all the good things
being said about git apply equally to other DVCSes such as Mercurial, bzr,
monotone, darcs, and Codeville.  All of these have very similar basic
models based on commit-before-merge and push/pull operations.  

It is not yet time to anoint git (or anything else) as a winner, even
by implication.  We will need to carefully consider the strengths and
weaknesses of each of these systems in relation to the specific needs
of the Emacs project.

I am working on an in-depth technical survey of this space.  You
can pull it at from a Mercurial repo at <http://thyrsus.com/hg/uvc/>.
As that indicates, I am leaning towards Mercurial for my own work --
but I intend to do a lot of research and testing before making a
final decision, and the results of my research will go into
that paper.

So far, I have done comparative evaluations of SCCS, RCS, CVS,
Subversion, Arch, and Monotone.  I intend to do similar ones of SVK,
git, bzr, darcs, Mercurial, and Codeville.  If I can get an evaluation
copy I will do Bitkeeper as well -- yes, it has a closed--source
license and there is thus no way I would recommend it, but it is of
some historical importance.

I also intend to write a test suite that will exercises all of these
in some known problem areas, especially near renames.  If I can 
come up with any way to do meaningful benchmarks, I will do that too.

So far, the only conclusion I am prepared to assert is that monotone,
darcs, and Codeville are not at present production-quality tools. I
am surveying them anyway because they have some important ideas in
them, and it is possible that they might become production-quality
tools in the future.

This leaves git, bzr, and Mercurial as near-term candidates for
production use from among the DVCSes.  All three have strikingly
similar functional models, though git is perhaps a bit more distant
from Mercurial and bzr than the latter two are from each other.

When my survey is done, we'll be in an extremely strong position to
make a selection based on hard facts and rigorous comparative analysis.
Until then, it's not time to choose among them or get too attached 
to any particular one.

(I would, by the way, welcome collaborators and reviewers to help
finish the survey.  It's a large job.  More hands would help.)
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

"Say what you like about my bloody murderous government," I says,
"but don't insult me poor bleedin' country."	-- Edward Abbey

             reply	other threads:[~2008-01-02 13:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 13:24 Eric S. Raymond [this message]
2008-01-02 13:30 ` It's not yet time to anoint git, or anything else Miles Bader
2008-01-02 14:07 ` Ted Zlatanov
2008-01-02 14:54   ` Tassilo Horn
2008-01-02 15:02     ` David Kastrup
2008-01-02 16:36     ` Ted Zlatanov
2008-01-02 19:28       ` Tassilo Horn
2008-01-02 19:58         ` Ted Zlatanov
2008-01-04  5:27       ` Richard Stallman
2008-01-02 14:09 ` Alan Mackenzie
2008-01-02 14:10   ` Miles Bader
2008-01-02 15:20   ` Eric S. Raymond
2008-01-02 14:51 ` Romain Francoise
2008-01-02 15:00   ` David Kastrup
2008-01-02 16:12     ` Andreas Schwab
2008-01-06 17:01     ` Andreas Schwab
2008-01-06 17:06       ` David Kastrup
2008-01-06 17:58         ` Andreas Schwab
2008-01-02 15:27   ` Eric S. Raymond
2008-01-02 17:04     ` Romain Francoise

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080102132458.387D9830B03@snark.thyrsus.com \
    --to=esr@snark.thyrsus.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.