From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Prefer Mercurial instead of git
Date: Sun, 05 Jan 2014 18:09:54 +0100 [thread overview]
Message-ID: <87ppo673tp.fsf@wanadoo.es> (raw)
In-Reply-To: 1388938726.11337.36.camel@Iris
Jordi Gutiérrez Hermoso <jordigh@octave.org> writes:
> On Sun, 2014-01-05 at 16:38 +0100, Óscar Fuentes wrote:
>> Jordi Gutiérrez Hermoso <jordigh@octave.org> writes:
>>
>> > We could adapt magit to use hg exactly the same way.
>>
>> Why do you insist on mentioning Magit?
>
> Because it's frequently loved and other people mention it as an
> advantage to using git with Emacs.
So you are mentioning *current* Emacs/git productivity tools as a bait
for fishing *git users* and gaining them for the hg cause because those
tools *could* be adapted to hg?
>> Its interface is modeled on git's characteristic features (index,
>
> hg queues
>
>> remotes,
>
> hg paths
>
>> etc)
>
> hg etc
No, thanks, I prefer the real thing.
>> Adapting it for hg would require a huge rewrite. You'll better write
>> your own package from scratch.
>
> I spoke with Sigma a while ago in #emacs (he was or is a big magit
> contributor, I can't recall his actual name), and he think it's
> feasible to abstract away the git part of magit and use it as an
> interface for git and hg.
Sure, and with a bit more of work it could be adapted to RCS too :-)
If you would be happy working with a hg-based Magit, why should you
object to working with a git-based Magit, once Emacs switches to git?
> Magit would hardly be the first of its kind
> to abstract away git and hg. Kiln Harmony has also done this, as has,
> for example, Phabricator.
>
>> Do you have Magit-envy? ;-)
>
> Not really. I'm trying to appeal to git Emacs users.
Have you considered the possibility that those users could be so
attached to git/Emacs as you can be to hg/Emacs? As git does the work
for me, why should I invest time on learning another tool that adds
*nothing* to my productivity?
But the issue here, as others already told you several times, is not
about which tool is best from the technical POV (both hg and git are
good enough, each with its own strong and weak points) but about
choosing the most popular and future-proof option. From this POV, going
with hg would be repeating the bzr mistake (well, not as bad, but a
mistake anyways.)
next prev parent reply other threads:[~2014-01-05 17:09 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 [this message]
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
-- 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=87ppo673tp.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--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.