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

Re: [PATCH] Fall back to three-way merge when applying a patch.

From
Linus Torvalds <torvalds@osdl.org>
Date
Oct 5, 2005, 14:30 UTC
Message-ID
<Pine.LNX.4.64.0510050725510.31407@g5.osdl.org>
In-Reply-To
<7vslvg1mcs.fsf@assigned-by-dhcp.cox.net>
On Tue, 4 Oct 2005, Junio C Hamano wrote:
> What is your workflow after seeing that the 47th patch among 175
> patches fails to apply?  I understand you run git-applymbox
> without -q, so it immediately fails and exits there.
Correct. 

What I usually do is to just ignore the split patches, and go back to the mbox. Delete the ones that applied, and look at the one that didn't. Then I try to apply that one manually - sometimes I actually do a quick manual branch to a known version, apply and merge - and I think I might try to use the "base wiggle" patch for that. Although I would actually prefer to be able to try against a specific named release (not "all named tags" first).

Quite often, the reason it doesn't apply is that I already have that patch through a git merge (or because I applied that patch earlier through another person), in which case I don't even try to merge it, I just delete that email too, and just do "git-applymbox" again.

		Linus
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 17 in “Fall back to three-way merge when applying a patch.”
  1. Fall back to three-way merge when applying a patch.Junio C Hamano, Oct 5, 2005
  2. Linus TorvaldsOct 5, 2005
  3. Junio C HamanoOct 5, 2005
  4. Linus TorvaldsOct 5, 2005
  5. Junio C HamanoOct 6, 2005
  6. Eric W. BiedermanOct 6, 2005
  7. Linus TorvaldsOct 6, 2005
  8. Junio C HamanoOct 6, 2005
  9. Eric W. BiedermanOct 6, 2005
  10. Linus TorvaldsOct 6, 2005
  11. Eric W. BiedermanOct 6, 2005
  12. Linus TorvaldsOct 6, 2005
  13. Eric W. BiedermanOct 6, 2005
  14. Show original and resulting blob object info in diff output.Junio C Hamano, Oct 7, 2005
  15. Linus TorvaldsOct 7, 2005
  16. Junio C HamanoOct 7, 2005
  17. Junio C HamanoOct 6, 2005

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.