From: Jay Soffian <jaysoffian@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Aghiles <aghilesk@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
git list <git@vger.kernel.org>
Subject: Re: potential improvement to 'git log' with a range
Date: Wed, 23 Jun 2010 16:45:07 -0400 [thread overview]
Message-ID: <AANLkTikcCQD9rFDscJNpLaRtX64occrXNHmrB-FdW69b@mail.gmail.com> (raw)
In-Reply-To: <7vmxulebr2.fsf@alter.siamese.dyndns.org>
On Wed, Jun 23, 2010 at 4:26 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Jay Soffian <jaysoffian@gmail.com> 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?
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.
next prev parent reply other threads:[~2010-06-23 20:45 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
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 [this message]
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=AANLkTikcCQD9rFDscJNpLaRtX64occrXNHmrB-FdW69b@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=aghilesk@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).