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

Re: merge conflict diff

From
JRJeremy Ramer <jdramer@gmail.com>
Date
Apr 3, 2008, 14:58 UTC
Message-ID
<b9fd99020804030758gced1981s624e50041904665c@mail.gmail.com>
In-Reply-To
<20080403142649.GA16699@coredump.intra.peff.net>
On Thu, Apr 3, 2008 at 8:26 AM, Jeff King <peff@peff.net> wrote:
Show 20 quoted lines
> On Thu, Apr 03, 2008 at 08:13:04AM -0600, Jeremy Ramer wrote:
>
>  > I am trying to figure out how to quickly diff two source files that
>  > led to a merge conflict.  When a conflict occurs the command
>  > [...]
>
> > So far I am thinking of
>  > # git checkout-index --stage=2 --temp foo
>  > # git checkout-index --stage=3 --temp foo
>  > # git diff .merge_x1 .merge_x2
>
>  The special ref syntax :<n>:file refers to the blob in stage <n> of the
>  index. So you can see them with:
>
>   git show :2:foo
>   git show :3:foo
>
>  Or diff them with:
>
>   git diff :2:foo :3:foo
Perfect! I was not aware of that syntax. That solves the question I asked.
>  You may also want to look at the git-mergetool script, which uses both
>  versions (along with the ancestor) as the arguments to many common merge
>  resolution programs.

This suggestion solves the actual problem in a much better way than I was thinking. Thanks for the help!

Previous: Jeff KingNext: Matthieu Moy
Message 3 of 4 in “merge conflict diff”
  1. Jeremy RamerApr 3, 2008
  2. Jeff KingApr 3, 2008
  3. Jeremy RamerApr 3, 2008
  4. Matthieu MoyApr 3, 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.