From: Karl Fogel <kfogel@red-bean.com>
To: "Jordi \\1 Hermoso" <jordigh@octave.org>
Cc: "esr@thyrsus.com" <esr@thyrsus.com>,
Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Prefer Mercurial instead of git
Date: Sat, 04 Jan 2014 20:14:28 -0600 [thread overview]
Message-ID: <87lhyv89a3.fsf@floss.red-bean.com> (raw)
In-Reply-To: <1388785952.11337.16.camel@Iris> ("Jordi \1 Hermoso"'s message of "Fri, 03 Jan 2014 16:52:32 -0500")
Jordi Gutiérrez Hermoso <jordigh@octave.org> writes:
>Please CC me in replies as I am not subscribed to this list.
>
>I know a majority opinion lies with git due to various cultural
>factors. I would, however, want to make a case for Mercurial being a
>better choice for a GNU package.
Heh. I started the original thread largely in order to take exactly
this poll in one thread -- that's why I included this line:
>Does anyone think we should stay on bzr, or choose a VCS other than git?
However, that thread has grown to contain at least one large side
discussion, and now we have a new thread that polls separately about
Mercurial. I suppose this was inevitable :-).
Anyway: I strongly favor Emacs choosing Git over Mercurcial.
I've used both systems, and don't find much practical difference between
them in most development situations. Their own maintenance communities
seem roughly equally healthy at this moment in time. I prefer Git
simply because it is winning the popularity war, which means that:
- When one searches the Web for help on a Git question, one is more
likely to find the answer quickly.
- When one seeks help directly from a person, that person is more
likely to be a) available and b) able to answer.
- Git is likely to be solidly maintained for decades into the future.
I do not have quite the same faith for Mercurial, though it does
look like it will be okay for at least a decade or so.
- More people are developing tools to work with Git than with
Mercurial. (Call it the "library" advantage, by analogy with
programming languages.)
- Skills I develop in Git can be reinvested in more other places than
skills I learn in Mercurial can be.
I don't see any really major technical reason to prefer either system;
my argument is just a standard positive feedback loop argument.
I'll happily use either, but if you're asking for votes, Git gets mine.
-K
next prev parent reply other threads:[~2014-01-05 2:14 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 21:52 Prefer Mercurial instead of git Jordi Gutiérrez Hermoso
2014-01-04 10:11 ` David Kastrup
2014-01-04 10:20 ` David Engster
2014-01-04 10:33 ` Eric S. Raymond
2014-01-04 13:13 ` Jordi Gutiérrez Hermoso
2014-01-04 13:29 ` David Engster
2014-01-04 14:23 ` David Kastrup
2014-01-04 14:38 ` Jordi Gutiérrez Hermoso
2014-01-04 15:19 ` David Kastrup
2014-01-04 15:24 ` Jordi Gutiérrez Hermoso
2014-01-04 16:51 ` David Engster
2014-01-04 17:16 ` Jordi Gutiérrez Hermoso
2014-01-04 17:31 ` David Engster
2014-01-04 17:40 ` Jordi Gutiérrez Hermoso
2014-01-04 18:34 ` Alan Mackenzie
2014-01-04 19:26 ` Óscar Fuentes
2014-01-04 20:18 ` Stefan Monnier
2014-01-05 11:07 ` Leo Liu
2014-01-04 17:35 ` Eli Zaretskii
2014-01-04 18:25 ` Paul Eggert
2014-01-04 20:03 ` Eli Zaretskii
2014-01-06 12:26 ` Darren Hoo
2014-01-06 14:58 ` Stefan Monnier
2014-01-06 17:44 ` Eli Zaretskii
2014-01-06 19:33 ` Paul Eggert
2014-01-04 14:40 ` Jordi Gutiérrez Hermoso
2014-01-05 12:17 ` Stephen J. Turnbull
2014-01-05 13:19 ` Jordi Gutiérrez Hermoso
2014-01-05 13:25 ` Florian Weimer
2014-01-05 13:55 ` Jordi Gutiérrez Hermoso
2014-01-05 15:38 ` Óscar Fuentes
2014-01-05 16:18 ` Jordi Gutiérrez Hermoso
2014-01-05 16:41 ` Eric S. Raymond
2014-01-05 17:09 ` Óscar Fuentes
2014-01-05 23:26 ` Jordi Gutiérrez Hermoso
2014-01-06 0:38 ` Óscar Fuentes
2014-01-06 1:01 ` Jordi Gutiérrez Hermoso
2014-01-06 0:03 ` David Kastrup
2014-01-05 17:54 ` Stephen J. Turnbull
2014-01-05 23:03 ` Dov Feldstern
2014-01-05 23:23 ` Karl Fogel
2014-01-05 23:37 ` Dov Feldstern
2014-01-06 4:02 ` Stephen J. Turnbull
2014-01-05 13:56 ` David Kastrup
2014-01-04 14:12 ` Rüdiger Sonderfeld
2014-01-04 16:08 ` Sebastian Wiesner
2014-01-04 16:41 ` Jordi Gutiérrez Hermoso
2014-01-04 18:37 ` David Kastrup
2014-01-04 18:44 ` Alan Mackenzie
2014-01-04 19:04 ` Jordi Gutiérrez Hermoso
2014-01-04 19:30 ` Óscar Fuentes
2014-01-05 16:23 ` Eli Zaretskii
2014-01-05 16:46 ` Eric S. Raymond
2014-01-05 17:03 ` Eli Zaretskii
2014-01-05 16:52 ` Óscar Fuentes
2014-01-05 17:17 ` Eli Zaretskii
2014-01-05 17:55 ` Óscar Fuentes
2014-01-05 18:07 ` Eli Zaretskii
2014-01-05 18:54 ` Óscar Fuentes
2014-01-05 21:07 ` Sean Sieger
2014-01-06 0:12 ` David Kastrup
2014-01-06 0:21 ` Rostislav Svoboda
2014-01-06 0:30 ` Karl Fogel
2014-01-06 2:24 ` Jay Belanger
2014-01-06 16:51 ` Karl Fogel
2014-01-06 17:13 ` Jay Belanger
2014-01-06 3:47 ` Eli Zaretskii
2014-01-05 3:13 ` Jay Belanger
2014-01-05 17:16 ` Sebastian Wiesner
2014-01-06 0:17 ` David Kastrup
2014-01-05 2:14 ` Karl Fogel [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-06 13:08 grischka
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=87lhyv89a3.fsf@floss.red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
--cc=jordigh@octave.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.