Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ongoing git vs hg (was: 5 days old?)

At Wed, 13 May 2020 14:14:16 +0200, Joerg Sonnenberger <> wrote:
Subject: Re: ongoing git vs hg (was: 5 days old?)
> The staging area is a general point of contention, even in the git
> world. Interactive commits (commit -i) and incrementally amending
> changes pretty much cover the general use cases without all the
> cognitive load another level of changes has.

Interactive commits that are driven by the tool are pointless as an
alternative for my use case of the Git staging area -- they are, by
definition, "interactive" i.e. not programmable.  The way most Git users
use the staging area with Git is in a way that can be considered
programmable, and the way many of us actually use the staging area is
indeed through other tools that drive Git programmatically, as is the
case with the tool called Magit that I use from within Emacs.

So, until/unless Magit (in my case) grows support for Mercurial, and/or
something even more usable appears in the Emacs world as a front-end for
Mercurial with similar capabilities, I'll continue using Magit and Git
in order to capture my work and the metadata about it into a change
management system.  That's just my personal limitation, but I suspect it
matches what other Git users, and especially Magit users, would prefer.

The question I have is then whether, and how, I can share such changes
and the captured metadata about them with the upstream project.  That's
done trivially with Git on both ends of course, but presumably Git can
also push changes to Mercurial in some lossless way as well (or vice
versa, Mercurial can pull changes, complete with their metadata, from a
Git repository).

> I have no idea what the OP is talking about. Mercurial doesn't have pull
> requests, neither does git BTW. So this is about some specific web UI or
> review tool, but I don't even know which one.

Consider "pull request" to stand in for _any_ kind of workflow and
mechanism that third parties would use to submit changes along with the
recorded existing metadata for those changes, to the upstream project's

					Greg A. Woods <>

Kelowna, BC     +1 250 762-7675           RoboHack <>
Planix, Inc. <>     Avoncote Farms <>

Attachment: pgpiOIV4YU4tf.pgp
Description: OpenPGP Digital Signature

Home | Main Index | Thread Index | Old Index