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

Re: Merging adjacent deleted lines?

From
Jay Soffian <jaysoffian@gmail.com>
Date
Jan 23, 2009, 07:18 UTC
Message-ID
<76718490901222318l7c3559ecje4a627fe2ff2ad12@mail.gmail.com>
In-Reply-To
<200901222113.31082.robin.rosenberg.lists@dewire.com>

On Thu, Jan 22, 2009 at 3:13 PM, Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:

Show 11 quoted lines
> torsdag 22 januari 2009 11:57:41 skrev Jonathan del Strother:
>> Mmm.  I use opendiff, which is generally ok, but in this case produced
>> a merge looking like this :
>>
>> http://pastie.org/paste/asset/367587/Picture_6.png
>>
>> Which, in my mind, isn't any clearer about the fact that both lines
>> ought to be deleted than the text conflict markers are.  Do any of the
>> other graphical tools present conflicts like that differently?
>
> Try a three-way merge tool instead like, e.g. xxdiff.

opendiff (aka FileMerge) *is* a three-way merge tool. If the screenshot above is not clear, I'm not sure what would be. The left pane shows your copy of the file with only line1, line3, and line4. The right pane shows the other copy, with only line1, line2, and line4.

The lower pane shows the merge resolution, which currently has the single conflict highlighted, and is being resolved toward the right. You can use the Action drop down menu to resolve the conflict one of five ways: left, right, both (left first), both (right first), neither. You've currently got "right" selected. The appropriate resolution is "neither", which keeps neither line3 from the left, nor line2 from the right.

Shrug.
j.
Previous: Robin RosenbergNext: Robin Rosenberg
Message 6 of 9 in “Merging adjacent deleted lines?”
  1. Jonathan del StrotherJan 21, 2009
  2. Robin RosenbergJan 21, 2009
  3. Junio C HamanoJan 21, 2009
  4. Jonathan del StrotherJan 22, 2009
  5. Robin RosenbergJan 22, 2009
  6. Jay SoffianJan 23, 2009
  7. Robin RosenbergJan 23, 2009
  8. Jay SoffianJan 23, 2009
  9. Jay SoffianJan 23, 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.