git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: specifying one-side of a merge commit?
Date: Thu, 12 Aug 2010 08:11:11 +0200	[thread overview]
Message-ID: <20100812061111.GA25026@atjola.homenet> (raw)
In-Reply-To: <AANLkTi=mnO8+XM4Bcjneaq+ngUSFesvZ_TYMRyy=f43a@mail.gmail.com>

On 2010.08.12 13:11:52 +0800, Tay Ray Chuan wrote:
> Hi,
> 
> I wonder how do you guys do this?
> 
> So far, what I've come up with is this:
> 
>   $ git rev-list $MERGE ^$MERGE^ | head -2 | tail -1
> 
> I'm sure there's a better way.

Are you looking for $MERGE^2? See SPECIFYING REVISIONS in
git-rev-parse(1).

Björn

      parent reply	other threads:[~2010-08-12  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12  5:11 specifying one-side of a merge commit? Tay Ray Chuan
2010-08-12  6:01 ` Elijah Newren
2010-08-12  6:11 ` Björn Steinbrink [this message]

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=20100812061111.GA25026@atjola.homenet \
    --to=b.steinbrink@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=rctay89@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).