All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: how to list commits on branch since last merge
Date: Tue, 08 Mar 2011 11:25:47 +0100	[thread overview]
Message-ID: <4D76042B.70005@drmicha.warpmail.net> (raw)
In-Reply-To: <AANLkTim_h6vbvnmy7oUNYmV82vCzLLfWKq=3_UY9kPYw@mail.gmail.com>

Jay Soffian venit, vidit, dixit 08.03.2011 11:11:
> On Tue, Mar 8, 2011 at 4:48 AM, Michael J Gruber
> <git@drmicha.warpmail.net> wrote:
>> You mean shorter than:
>>
>> git rev-list --merges -1 $(git merge-base foo bar)
>>
>> Or maybe I'm misunderstanding "contain".
> 
> Going back to my original picture, I mean commit m:
> 
>   o---o---x---o---...    foo
>    \       \
>     o---o---m---o---...  bar
> 
> merge-base foo bar gives me x; to get m I then need to grep the output
> of rev-list --parents for x.
> 
> j.

Maybe

git rev-list --ancestry-path --merges $(git merge-base foo bar)..bar

or, with the patch in pu

git rev-list --ancestry-path --merges --right-only foo...bar

each piped into tail -1 ?

Michael

  reply	other threads:[~2011-03-08 10:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08  7:24 how to list commits on branch since last merge Jay Soffian
2011-03-08  8:48 ` Michael J Gruber
2011-03-08  9:35   ` Jay Soffian
2011-03-08  9:39     ` Michael J Gruber
2011-03-08  9:43     ` Jay Soffian
2011-03-08  9:48       ` Michael J Gruber
2011-03-08 10:11         ` Jay Soffian
2011-03-08 10:25           ` Michael J Gruber [this message]
2011-03-08 17:12           ` Jeff King
2011-03-08 17:39             ` Jay Soffian
2011-03-08 18:05               ` Jeff King
2011-03-08 19:08             ` Andreas Schwab
2011-03-08 21:03               ` Jeff King

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=4D76042B.70005@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=jaysoffian@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.