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

Re: Merge format documented?

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 23, 2009, 07:52 UTC
Message-ID
<7viqm08ymb.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<200903230818.20044.agruen@suse.de>
Andreas Gruenbacher <agruen@suse.de> writes:
Show 13 quoted lines
> On Monday, 23 March 2009 4:50:24 Junio C Hamano wrote:
>> Andreas Gruenbacher <agruen@suse.de> writes:
>> > is the format that git normally uses for indicating merge conflicts in
>> > files (the <<< === >>> markers) documented somewhere?  How exactly does
>> > it differ from the diff3 format (<<< ||| === >>>)?  Diff3's -m mode seems
>> > to come close to what git does, except that git doesn't produce the |||
>> > section:
>>
>> It is an imitation of output from "merge" program of RCS suite Paul you
>> know maintains ;-)
>
> So it's the same format except that diff3's ||| section isn't shown. I was 
> wondering if there are any additional tricks.
No additional tricks.

As far as I can remember, the format was not really chosen, but simply fell out as a natural consequence of using "merge" rather than "diff3" as a merge backend (we originally used to invoke "merge" from RCS suite instead of performing file-level merges ourselves), but we could say we chose "merge" over "diff3 -m" because the output format should be more familiar than the diff3-m format with |||, especially to anybody who came from subversion or CVS background.

Previous: Andreas GruenbacherNext: Johannes Sixt
Message 4 of 6 in “Merge format documented?”
  1. Andreas GruenbacherMar 23, 2009
  2. Junio C HamanoMar 23, 2009
  3. Andreas GruenbacherMar 23, 2009
  4. Junio C HamanoMar 23, 2009
  5. Johannes SixtMar 23, 2009
  6. Jakub NarebskiMar 27, 2009

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.