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

Re: git merge conflict resolution?

From
Björn Steinbrink <b.steinbrink@gmx.de>
Date
Sep 25, 2009, 09:58 UTC
Message-ID
<20090925095831.GA17721@atjola.homenet>
In-Reply-To
<1253841510.18126.10.camel@Joe-Laptop.home>
On 2009.09.24 18:18:30 -0700, Joe Perches wrote:
> Question about how git does merge conflict resolution.
> 
> This patch doesn't really apply, and the results after the
> patch aren't what at least I expect.
[...]
> Russell's patch removes the "(moderated for non-subscribers)"
> from each entry, yet the final result includes it.
> 
> Can someone help me understand why?
If you look at baea7b946f00a291b166ccae7fcfed6c01530cc6, you see:
    Merge branch 'origin' into for-linus
    Conflicts:
        MAINTAINERS

Git was unable to automatically merge that file, as there were conflicting changes. That merge was done by Russel King, and _he_ decided that the result should include the "(moderated for ...)" part.

Björn
Previous: Joe Perches
Message 2 of 2 in “git merge conflict resolution?”
  1. Joe PerchesSep 25, 2009
  2. Björn SteinbrinkSep 25, 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.