git/list[1] front-page[2] threads[3] people[4] search[5] about
 

How do I label conflict blocks in merge-recursive output?

From
しらいしななこ <nanako3@bluebottle.com>
Date
Jun 29, 2007, 14:28 UTC
Message-ID
<20070629232849.6117@nanako3.bluebottle.com>
Hi, I am updating my 'git-save' script and have a question.  
When I play back the state previously recorded, I run:
   $ git-merge-recursive $base -- HEAD $stash

This is done after getting the $base (the state the stash was made from), and $stash (the state of the interrupted work recorded in the stash) in these variables. When there are conflicts, I see '<<<<<<<' and '>>>>>>>' markers in the merged file.

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.

In a real conflict after a 'git-pull', I think I saw nicer labels that are not hexadecimal strings after these markers.

How do I tell merge-recursive to do that? I tried to read the documentation for merge-recursive but there is no manual page.

TIA
-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/

----------------------------------------------------------------------
Find out how you can get spam free email.
http://www.bluebottle.com
Next: Johannes Schindelin
Message 1 of 2 in “How do I label conflict blocks in merge-recursive output?”
  1. しらいしななこJun 29, 2007
  2. Johannes SchindelinJun 29, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.