From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Display 'theirs' branch name when possible in merge.
Date: Sat, 23 Dec 2006 10:11:28 +0100 [thread overview]
Message-ID: <emirms$kh3$1@sea.gmane.org> (raw)
In-Reply-To: 20061223084447.GB10203@spearce.org
Shawn O. Pearce wrote:
> Displaying the SHA1 of 'their' branch (the branch being merged into
> the current branch) is not nearly as friendly as just displaying
> the name of that branch, especially if that branch is already local
> to this repository.
>
> git-merge now sets the environment variable 'GITHEAD_%(sha1)=%(name)'
> for each argument it gets passed, making the actual input name that
> resolved to the commit '%(sha1)' easily available to the invoked
> merge strategy.
>
> git-merge-recursive makes use of these environment variables when
> they are available by using '%(name)' whenever it outputs the commit
> identification rather than '%(sha1)'. This is most obvious in the
> conflict hunks created by xdl_merge:
>
> $ git mege sideb~1
git merge sideb~1
> <<<<<<< HEAD:INSTALL
> Good!
> =======
> Oops.
> >>>>>>> sideb~1:INSTALL
Very nice. Thanks.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2006-12-23 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6115ec06459724c7c37c355805462cb61715e9c5.1166863413.git.spearce@spearce.org>
2006-12-23 8:44 ` [PATCH 2/2] Display 'theirs' branch name when possible in merge Shawn O. Pearce
2006-12-23 9:11 ` Jakub Narebski [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='emirms$kh3$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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 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.