From: Jakub Narebski <jnareb@gmail.com>
To: Martin Geisler <mg@lazybytes.net>
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 23:24:31 +0200 [thread overview]
Message-ID: <201006232324.32516.jnareb@gmail.com> (raw)
In-Reply-To: <877hlpimkq.fsf@hbox.dyndns.org>
On Wed, 23 Jun 2010, Martin Geisler wrote:
> 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).
Err... so how it is for X..Y / X::Y in Mercurial? "Ancestors of Y,
excluding ancestors of X" is larger range (and default result for
X..Y in Git) than "descendants of X and ancestors of Y" (i.e. the
result of new --ancestry-path X..Y in Git).
See http://repo.or.cz/w/git.git/blob/refs/heads/pu:/Documentation/rev-list-options.txt#l582
>>>> [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?
Well, I do provide disclaimer upfront that I am biased towards Git, and
I have tried to be objective.
But I don't mind if someone who uses Mercurial fixed that side, and
tried for neutral point of view (but not introducing the opposite bias).
There would be problem with NPOV with issues without clear answer, where
personal preference matters, though.
>> P.S. Isn't mercurial-devel subscribe only?
>
> No, not really -- you will be whitelisted the first time you post.
Nice.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-06-23 21:24 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
2010-06-23 21:24 ` Jakub Narebski [this message]
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=201006232324.32516.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=aghilesk@gmail.com \
--cc=git@vger.kernel.org \
--cc=mercurial-devel@selenic.com \
--cc=mg@lazybytes.net \
--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).