Re: potential improvement to 'git log' with a range

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: potential improvement to 'git log' with a range

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:48:59

Jay Soffian [off-list ref] writes:
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. :-)
Doesn't "git show -p --first-parent $merge" work for you?

Re: potential improvement to 'git log' with a range

From: Jay Soffian <hidden>
Date: 2016-06-15 22:48:59

On Wed, Jun 23, 2010 at 4:26 PM, Junio C Hamano [off-list ref] wrote:
Jay Soffian [off-list ref] writes:
quoted
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. :-)
Doesn't "git show -p --first-parent $merge" work for you?
I don't understand at all. Isn't -p redundant with git show? And how
is --first-parent $merge equivalent to
$merge_commit^..$merge_commit^2? I literally want a list of all the
commits brought in by the merge.

Confusedly yours,

j.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help