git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jay Soffian <jaysoffian@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git <git@vger.kernel.org>
Subject: Re: how to list commits on branch since last merge
Date: Tue, 8 Mar 2011 04:43:26 -0500	[thread overview]
Message-ID: <AANLkTikK8Uc8=wKROYWWxZ_6OtQtqBmFCZN760M1LO+c@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinOEutM92k4SUGEXbfTpzGcQitpW4CZbcQbg0R4@mail.gmail.com>

On Tue, Mar 8, 2011 at 4:35 AM, Jay Soffian <jaysoffian@gmail.com> wrote:
> On Tue, Mar 8, 2011 at 3:48 AM, Michael J Gruber
> <git@drmicha.warpmail.net> wrote:
>> 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 ;)
>
> Ah. The rev-list man page entry on --ancestry-path only talks about
> using it with '..', so I didn't even try it with the symmetric diff
> operator ('...').

And with the clue to use '...', it's easy:

  $ git log --ancestry-path foo...bar ^foo

Still want an easy way for merge-base to report the merge which
contains the merge-base. That will wait for another day.

j.

  parent reply	other threads:[~2011-03-08  9:44 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 [this message]
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='AANLkTikK8Uc8=wKROYWWxZ_6OtQtqBmFCZN760M1LO+c@mail.gmail.com' \
    --to=jaysoffian@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.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).