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

Merge only complete commits

From
Ittay Dror <ittay.dror@gmail.com>
Date
Sep 3, 2008, 13:52 UTC
Message-ID
<48BE96BA.1000106@gmail.com>
Hi,

Starting with '12345678', one branch creates a change '1A345678', the other '1B345C78'. Merging of the branches will result in '1<A=B>345C78'.

But isn't it logical to assume that if changes 'B' and 'C' were done in the same commit, then they are related and so a conflict in one implicitly means a conflict in the whole commit?

Of course, in a case of a single file, with a single commit, it is easy to detect. But what if there have been a history of commits before the merge, or if several files were changed?

Maybe help me find the commit by including them in the RCS conflict markers?

Ittay
-- 
--
Ittay Dror <ittay.dror@gmail.com>
Message 1 of 1 in “Merge only complete commits”
  1. Ittay DrorSep 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.