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

Re: "Temporary merge branch 2" Conflicts

From
SBStephen Bash <bash@genarts.com>
Date
Aug 20, 2012, 13:21 UTC
Message-ID
<1666100271.191032.1345468901838.JavaMail.root@genarts.com>
In-Reply-To
<7vfw7lteaw.fsf@alter.siamese.dyndns.org>
----- Original Message -----
Show 18 quoted lines
> From: "Junio C Hamano" <gitster@pobox.com>
> Sent: Friday, August 17, 2012 5:10:47 PM
> Subject: Re: "Temporary merge branch 2" Conflicts
> 
> Stephen Bash <bash@genarts.com> writes:
> 
> > What is the recommended method for resolving this sort of merge?
> > kdiff3 obviously doesn't understand the situation.  Do the working
> > tree files contain all the conflicts?  If so, I can just go
> > through by hand and resolve the conflicts the old fashion way.
> 
> Yes.  External tools like kdiff3 may not understand the conflict in
> the working tree, but the files in the working tree should have
> resolved the naturally resolvable bits and only left the conflicted
> bits conflicted.  Just resolve manually if you can, and then look at
> what both branches wanted to do to the file ("git log -p --merge
> $that_path" before you "git add" as the final sanity check would
> work nicely) to make sure your resolution makes sense.
Thanks for the clarification Junio.  I'll take another swipe at it this week now that I know what I'm doing!
Stephen
Previous: Junio C Hamano
Message 4 of 4 in “"Temporary merge branch 2" Conflicts”
  1. Stephen BashAug 17, 2012
  2. Stephen BashAug 17, 2012
  3. Junio C HamanoAug 17, 2012
  4. Stephen BashAug 20, 2012

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.