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

[PATCH 0/2] Fail merge gently

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Dec 3, 2007, 05:32 UTC
Message-ID
<Pine.LNX.4.64.0712030025032.5349@iabervon.org>

This series makes it possible to call unpack_trees() and get an error result instead of having it call die(). Additionally, it allows the caller to suppress error messages, in case it's just going to try something else instead of actually failing. This passes all of the tests, and should have no effect on existing code except for making the exit messages not say "fatal:", and merge-recursive will free its tree cache before exiting, and print an additional message already in the code but previously inaccessible.

This is preliminary for builtin-checkout, which I'm partway through. I think I'm down to the case where a real merge is needed for -m, but I'm not sure, and I think I need to write a bunch of tests for checkout.

Daniel Barkalow (2):
      Allow callers of unpack_trees() to handle failure
      Add flag to make unpack_trees() not print errors.
 builtin-read-tree.c |    3 +-
 unpack-trees.c      |   90 ++++++++++++++++++++++++++++++---------------------
 unpack-trees.h      |    1 +
 3 files changed, 56 insertions(+), 38 deletions(-)
	-Daniel
*This .sig left intentionally blank*
Message 1 of 1 in “Fail merge gently”
  1. 0/2 Fail merge gentlyDaniel Barkalow, Dec 3, 2007

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.