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

Re: [RFC] Introduce git-xxdiff to invoke xxdiff for manual conflict resolution

From
Jeff King <peff@peff.net>
Date
Aug 4, 2006, 03:31 UTC
Message-ID
<20060804033144.GB24818@coredump.intra.peff.net>
In-Reply-To
<44D296D8.4030200@catalyst.net.nz>
On Fri, Aug 04, 2006 at 12:37:44PM +1200, Martin Langhoff (CatalystIT) wrote:
Show 11 quoted lines
> >instead check for stage 2 ("ours") for the path.
> Reading Documentation/git-read-tree.txt it seems to mean that stage 1 is 
> merge base, 1 is ours and 2 is the branch being merged in.
> 
> I am confused...
> 
> Quote:
> >When performing a merge of another
> >branch into the current branch, we use the common ancestor tree
> >as <tree1>, the current branch head as <tree2>, and the other
> >branch head as <tree3>.
Look further down:
   OK, this all sounds like a collection of totally nonsensical rules,
   but it's actually exactly what you want in order to do a  fast
   merge.  The different stages  represent the "result tree" (stage 0,
   aka "merged"), the original tree (stage 1, aka "orig"), and the two
   trees you are trying to merge (stage 2 and 3 respectively).

HTH, -Peff

Previous: Martin Langhoff (CatalystIT)Next: Martin Langhoff (CatalystIT)
Message 8 of 9 in “[RFC] Introduce git-xxdiff to invoke xxdiff for manual conflict resolution”
  1. Martin LanghoffAug 3, 2006
  2. Junio C HamanoAug 4, 2006
  3. Martin Langhoff (CatalystIT)Aug 4, 2006
  4. [RFC] Introduce git-xxdiff to invoke xxdiff for manual conflict resolution - take 2Martin Langhoff, Aug 4, 2006
  5. Alex RiesenAug 4, 2006
  6. Martin LanghoffAug 5, 2006
  7. Martin Langhoff (CatalystIT)Aug 4, 2006
  8. Jeff KingAug 4, 2006
  9. Martin Langhoff (CatalystIT)Aug 4, 2006

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.