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

Re: Wrong conflicts on file splits

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
May 4, 2009, 13:27 UTC
Message-ID
<49FEED2C.8010501@drmicha.warpmail.net>
In-Reply-To
<9e4733910905040553u377ab11n1609d980021be498@mail.gmail.com>
Jon Smirl venit, vidit, dixit 04.05.2009 14:53:
Show 18 quoted lines
> I keep running into this problem, is there anything I can do to make
> it better? I'm using stgit but this is a problem in git itself.
> 
> I have a patch that splits file A into two files, A and B.
> Now I merge with another tree and bring in a one line fix to A.
> The fix touches the pre-split file A in a section that is going to end up in B.
> Next I re-apply the patch that splits A into A and B.
> 
> This results in a large conflict in the post split file A.
> And no patch being applied to file B which is where the fix belongs.
> 
> Repeat this process with a multi-line fix and the whole automated
> merge process breaks down and I have to carefully figure everything
> out by hand.
> 
> The merge process seems to be unaware of the newly created file B. No
> patches or conflict ever end up in it.
> 

Can you provide a test case or at least a list of commands which you are issuing? You complain about "merge", but you say you are "applying a patch". Are you merging that patch from another branch, or are you really applying it as a patch (git-apply/cherry-pick/rebase/what-not)?

Cheers, Michael

Previous: Jon SmirlNext: Jon Smirl
Message 2 of 7 in “Wrong conflicts on file splits”
  1. Jon SmirlMay 4, 2009
  2. Michael J GruberMay 4, 2009
  3. Jon SmirlMay 4, 2009
  4. Michael J GruberMay 4, 2009
  5. Jon SmirlMay 4, 2009
  6. Michael J GruberMay 4, 2009
  7. Jon SmirlMay 4, 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.