git.vger.kernel.org archive mirror
 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 09:48:50 +0100	[thread overview]
Message-ID: <4D75ED72.8030203@drmicha.warpmail.net> (raw)
In-Reply-To: <AANLkTi=zW9hOhnddw6HsjQwV2qLf_R_qeNna+XeN6U6x@mail.gmail.com>

Jay Soffian venit, vidit, dixit 08.03.2011 08:24:
> Given this history:
> 
> o---o---x---o---...    foo
>  \       \
>   o---o---m---o---...  bar
> 
> I want to list the commits on bar newer than merge m (the last merge
> from foo). merge-base returns x.
> 
> I feel like I'm going to face-palm upon reply, but the only way I see
> to do it is:
> 
>   $ git rev-list --ancestry-path $(git merge-base foo bar)..bar
> 
> Or by greping the output of rev-list --merges --parents foo..bar
> looking for the merge base.
> 
> I must be missing something obvious, since this feels like it should
> be a common operation. :-)

Have you tried:

git rev-list --ancestry-path --left-right foo...bar

If the ">" commits are the ones that you want you only have to wait for
the "--right-only" option which is cooking in pu. And grep '^>' for now ;)

Michael

  reply	other threads:[~2011-03-08  8:52 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 [this message]
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
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=4D75ED72.8030203@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 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).