From: "François Orieux" <orieux@iap.fr>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>,
"Neal Becker" <ndbecker2@gmail.com>,
emacs-devel@gnu.org
Subject: Re: preferring mercurial
Date: Fri, 10 Jan 2014 10:54:30 +0100 [thread overview]
Message-ID: <87txdc5fhl.fsf@gaia.iap.fr> (raw)
In-Reply-To: <87iottf4fe.fsf@uwakimon.sk.tsukuba.ac.jp>
"Stephen J. Turnbull" <stephen@xemacs.org> writes:
> François Orieux writes:
>
>> My resume of all the posts I have read is that git and hg are
>> technically equivalent.
>
> [...] but git exposes a much cleaner interface to the internal model
> of blobs (file content), trees (file directories), and commits *to the
> user*.
>
> [...] I don't know about Mercurial, haven't looked at its internals.
I don't know to, but you can't say "git is better" and say after you
don't know about hg.
>> Hg is cleaner, easier with better doc and ui
>
> I disagree, but again it's a matter of taste.
By using both, we can't really say it's a matter of taste. By reading
doc we can't to. Or by reading all these pages on internet, like
http://stevelosh.com/blog/2013/04/git-koans/
>> with a bigger respect of history.
>
> That is a lie, and you should stop repeating it, and tell people who
> try to tell it to you to stop, too.
>
> Nothing has more respect for history than git. Using git, you can
> forget history (by deleting or moving refs) but you can't change it or
> delete it.[1] [...]
Ok I didn't know that point and I will stop.
Git is excellent and a good choice for emacs. But by taking into account
all the pro and cons of both tools, we must admit that the sole thing
that really remains is that git is popular: git is chosen because
"everybody" chose this tool. Why not afterall.
--
IAP, CNRS-UPMC - Paris, France
+33 1 73 77 55 11
http://research.orieux.fr
next prev parent reply other threads:[~2014-01-10 9:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 12:35 preferring mercurial Neal Becker
2014-01-09 13:11 ` Tim Visher
2014-01-09 13:53 ` Neal Becker
2014-01-09 13:44 ` Rüdiger Sonderfeld
2014-01-09 14:49 ` François Orieux
2014-01-09 17:31 ` Stephen J. Turnbull
2014-01-10 9:54 ` François Orieux [this message]
2014-01-10 11:48 ` Nathan Trapuzzano
2014-01-10 12:44 ` Stephen J. Turnbull
2014-01-10 11:50 ` Stephen J. Turnbull
2014-01-10 13:59 ` Stefan Monnier
2014-01-10 14:08 ` Eric S. Raymond
2014-01-10 15:22 ` Jordi Gutiérrez Hermoso
2014-01-10 15:55 ` Eric S. Raymond
2014-01-10 16:09 ` Jordi Gutiérrez Hermoso
2014-01-10 16:21 ` Eli Zaretskii
2014-01-11 7:15 ` Richard Stallman
2014-01-10 15:03 ` Jordi Gutiérrez Hermoso
2014-01-10 19:20 ` Stephen J. Turnbull
2014-01-10 19:54 ` David Engster
2014-01-10 19:55 ` Jordi Gutiérrez Hermoso
2014-01-11 15:55 ` Stephen J. Turnbull
2014-01-11 16:37 ` David Kastrup
2014-01-15 17:07 ` Martin Geisler
2014-01-15 16:49 ` Martin Geisler
2014-01-09 15:42 ` Yuri Khan
2014-01-10 15:16 ` Jordi Gutiérrez Hermoso
2014-01-09 20:28 ` Barry Warsaw
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=87txdc5fhl.fsf@gaia.iap.fr \
--to=orieux@iap.fr \
--cc=emacs-devel@gnu.org \
--cc=ndbecker2@gmail.com \
--cc=ruediger@c-plusplus.de \
--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.