git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Geisler <mg@lazybytes.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	mercurial list <mercurial-devel@selenic.com>,
	git list <git@vger.kernel.org>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	Aghiles <aghilesk@gmail.com>
Subject: Re: potential improvement to 'git log' with a range
Date: Wed, 23 Jun 2010 21:19:17 +0200	[thread overview]
Message-ID: <877hlpimkq.fsf@hbox.dyndns.org> (raw)
In-Reply-To: <201006232002.18921.jnareb@gmail.com> (Jakub Narebski's message of "Wed, 23 Jun 2010 20:02:17 +0200")

[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]

Jakub Narebski <jnareb@gmail.com> writes:

> On Wed, 23 Jun 2010, Martin Geisler wrote:
>
>> This is fixed with Mercurial 1.6: we now have a query language where
>> 'X..Y' (or 'X::Y') is understood as the set of changesets that are
>> both descendents of X and ancestors of Y.
>
> Thanks. It looks like Mercurial's 'X::Y' is equivalent to Git's
> '--ancestry-path X..Y' (the --ancestry-path option is a new feature).

Yeah, it is equivalent to --ancestry-path. I had no idea Git's range
operator worked the way it does :-)

For mercurial-devel: 'X..Y' is a shorthand for '^X Y', which in turn
means ancestors of Y, excluding ancestors of X (and excluding X).

>>> [1]
>>> http://stackoverflow.com/questions/1598759/git-and-mercurial-compare-and-contrast/1599930#1599930
>
> Fixed. Could you please take a look if it is correct, and if there are
> errors, either correct it yourself, or ask me to do it (either via
> comments for this question, or via email)? Thanks in advance.

Yes, its correct now. But would you object if I or someone else took out
all those personal opinions and rewrote it from a neutral point of view?

> P.S. Isn't mercurial-devel subscribe only?

No, not really -- you will be whitelisted the first time you post.

-- 
Martin Geisler

Mercurial links: http://mercurial.ch/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-06-23 19:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 23:24 potential improvement to 'git log' with a range Aghiles
2010-04-09 23:33 ` Santi Béjar
2010-04-09 23:33 ` Sverre Rabbelier
2010-04-10  0:13   ` Aghiles
2010-04-10  0:16     ` Sverre Rabbelier
2010-04-10  1:20     ` Linus Torvalds
2010-04-11 20:31       ` Aghiles
2010-04-11 21:32       ` Jakub Narebski
2010-06-23 17:05         ` Martin Geisler
2010-06-23 18:02           ` Jakub Narebski
2010-06-23 19:19             ` Martin Geisler [this message]
2010-06-23 21:24               ` Jakub Narebski
2010-06-23 22:04                 ` Martin Geisler
2010-06-23 19:36       ` Jay Soffian
2010-06-23 20:26         ` Junio C Hamano
2010-06-23 20:45           ` Jay Soffian
2010-06-24 20:31           ` Junio C Hamano
2010-06-24 22:49             ` Jay Soffian

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=877hlpimkq.fsf@hbox.dyndns.org \
    --to=mg@lazybytes.net \
    --cc=aghilesk@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=mercurial-devel@selenic.com \
    --cc=srabbelier@gmail.com \
    --cc=torvalds@linux-foundation.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).