From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: しらいしななこ <nanako3@bluebottle.com>
Cc: GIT <git@vger.kernel.org>
Subject: Re: How do I label conflict blocks in merge-recursive output?
Date: Fri, 29 Jun 2007 18:16:00 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706291806120.4438@racer.site> (raw)
In-Reply-To: <20070629232849.6117@nanako3.bluebottle.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1083 bytes --]
Hi,
On Fri, 29 Jun 2007, しらいしななこ wrote:
> A trouble I am seeing is that there are large hexadecimal string after
> these markers, like this:
>
> <<<<<<< 13bd5d46b4a5d4ef44c53fab11e74801c18b16d0:A
> side
> revision
> =======
> local
> modification
> >>>>>>> 9aa4ad6a3bdf5340bed969f6e14abb4e07e794f7:A
>
> I do not know what object these are, and I do not think it is useful to
> show them to the user. I want them to say something more useful.
>
> [...]
>
> How do I tell merge-recursive to do that? I tried to read the
> documentation for merge-recursive but there is no manual page.
Yes, it is unfortunately undocumented. To override the name for a given
SHA-1 (which is the long hex string, and which you can obtain by
"git-rev-parse <commit>"), set the environment variable
GITHEAD_<sha1>="This is a much nicer message"
IOW If you would have done this (_before_ calling merge-recursive):
export GITHEAD_9aa4ad6a3bdf5340bed969f6e14abb4e07e794f7=nanako
then the last conflict marker would have read
>>>>>>> nanako:A
Hth,
Dscho
prev parent reply other threads:[~2007-06-29 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 14:28 How do I label conflict blocks in merge-recursive output? しらいしななこ
2007-06-29 17:16 ` Johannes Schindelin [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=Pine.LNX.4.64.0706291806120.4438@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=nanako3@bluebottle.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).