Re: potential improvement to 'git log' with a range
- From
Jay Soffian <jaysoffian@gmail.com>
- Date
- Jun 23, 2010, 19:36 UTC
- Message-ID
- <AANLkTinPrObdQh1vZLo0tlq2bZn7BXKvHWLktI2pR5LY@mail.gmail.com>
- In-Reply-To
- <alpine.LFD.2.00.1004091807220.3558@i5.linux-foundation.org>
On Fri, Apr 9, 2010 at 9:20 PM, Linus Torvalds <torvalds@linux-foundation.org> wrote:
Show 10 quoted lines
> To make things even more exciting triple-dot, "A...B" has two different
> meanings too, again one that is about sets ("symmetric difference") for
> the log-based ones, and one that is a somewhat badly defined range for the
> diff based ones (where the end-points are "one common nearest ancestor of
> A and B" and "B" respectively).
>
> It's all actually very natural when you get used to it, although that
> "A...B" as a range really isn't well-defined, since there can be more than
> one common nearest ancestors. It's still often enough useful in practice
> that I wouldn't get rid of it, but it's not the greatest feature.Speaking of which, I'd love a switch to "git show $merge_commit" which does "git log $merge_commit^..$merge_commit^2" but I've been too lazy to write it. 9/10 times that I use .., it's in this context. :-)
j.