From: David Kastrup <dak@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: "Jordi Gutiérrez Hermoso" <jordigh@octave.org>, emacs-devel@gnu.org
Subject: Re: Prefer Mercurial instead of git
Date: Sun, 05 Jan 2014 14:56:24 +0100 [thread overview]
Message-ID: <87d2k6ilbr.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <8738l2k4hh.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Sun, 05 Jan 2014 21:17:14 +0900")
"Stephen J. Turnbull" <stephen@xemacs.org> writes:
> Jordi Gutiérrez Hermoso writes:
>
> > I don't think Stephen's a particular expert in this
>
> I don't either. But since I'm not an expert, why listen to me?
> Listen to Barry Warsaw and Karl Fogel, who invited me to coauthor,
> instead:
>
> http://www.python.org/doc/peps/pep-0374/
> http://www.emacswiki.org/BzrForEmacsDevs
>
> And to get David K to recommend me given how often we've been at each
> others' throats
Locking horns. Different thing.
> over the decades is a pretty good trick, one I'm proud of.
<URL:http://drmcninja.com/archives/comic/21p97/>
> Nevertheless, as ESR and DAK have been at pains to point out, the
> problem with Mercurial, like the problem with Bazaar, isn't technical.
>
> The problem is that Mercurial isn't git. Git definitely is the leader
> now. Git is "cool". Git is more flexible (neither Mercurial nor
> Bazaar can support workflows that use colocated branches heavily).
> Git has more growth potential: new techniques for manipulating DAGs
> are developed in and for git. (They can't be developed *in* Mercurial
> or Bazaar command language, you have to go to Python level to develop
> useful new features.) Mercurial's supporting applications don't seem
> to improve as quickly (at least, not those distributed with Mercurial,
> cf. gitk vs. hg view). So git is clearly winning the popularity
> contest, both in general and on emacs-devel.
There is actually another problem here: with regard to Software Freedom,
Git is in the "good enough" category. People are comfortable using it.
And that's something which, in the big order of things, we should
consider as a win. However, services like Github try locking people
into their proprietary services. And are succeeding. The software
Github runs on is proprietary, and the usage conditions are pretty
onerous. Yes, one can pull repositories from them, but the entire other
workflow they offer to users is locked down.
Of course, it is the Facebook effect at work again: if you build a
_business_ model around gratis services, your product is not the
service, but the users.
The tool Git itself does not care what it is used for, and Git upstream
is also not overly interested as long as the conditions on Git itself
are kept.
The Git universe is unlike the Windows universe: it does not strongly
prefer proprietary thinking and workflows.
And yet we do try to bring the value of freedom also to Windows users,
like when providing Emacs.
I think there is more at stake by turning the back on Git. It is too
important as a free tool to let the proprietary vendors determine the
directions how "everybody" is going to use it, under their control, with
their ultimate weapon: convenience.
If we don't offer answers of our own, we forfeit the game. There are
games which are loaded against us anyway, where there is little point in
playing to lose. But this one's right at our door.
--
David Kastrup
next prev parent reply other threads:[~2014-01-05 13:56 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 [this message]
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
-- 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=87d2k6ilbr.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jordigh@octave.org \
--cc=stephen@xemacs.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.