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

Re: [PATCH 2/2] git-merge documentation: describe how conflict is presented

From
Jakub Narebski <jnareb@gmail.com>
Date
Sep 1, 2008, 10:29 UTC
Message-ID
<g9gg5l$b55$1@ger.gmane.org>
In-Reply-To
<7vwshwz8gf.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
> +By default, git uses the same style as that is used by "merge" program
> +from the RCS suite to present such a conflicted hunk, like this:

Actually it is also one of diff3 output format, to be more exact it is format generated by "diff3 -E"/"diff3 --show-overlap"

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 3 in “git-merge documentation: describe how conflict is presented”
  1. 2/2 git-merge documentation: describe how conflict is presentedJunio C Hamano, Sep 1, 2008
  2. Jakub NarebskiSep 1, 2008
  3. Junio C HamanoSep 1, 2008

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.