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

[PATCH 2/5] Don't output 'Automatic merge failed, ...'

From
Fredrik Kuivinen <freku045@student.liu.se>
Date
Sep 13, 2005, 21:40 UTC
Message-ID
<20050913214023.GC10953@c165.ib.student.liu.se>
In-Reply-To
<20050913213730.GA10953@c165.ib.student.liu.se>
git-merge.sh does this for us.
Signed-off-by: Fredrik Kuivinen <freku045@student.liu.se>
---
 git-merge-recursive.py |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)
e0e1a108a224b6bf202beb59c1514325205d3638
diff --git a/git-merge-recursive.py b/git-merge-recursive.py
--- a/git-merge-recursive.py
+++ b/git-merge-recursive.py
@@ -423,5 +423,4 @@ except:
 if clean:
     sys.exit(0)
 else:
-    print 'Automatic merge failed, fix up by hand'
     sys.exit(1)
Previous: Fredrik KuivinenNext: Fredrik Kuivinen
Message 3 of 6 in “More recursive merge updates”
  1. 0/5 More recursive merge updatesFredrik Kuivinen, Sep 13, 2005
  2. 1/5 Be more like the 'resolve' strategy.Fredrik Kuivinen, Sep 13, 2005
  3. 2/5 Don't output 'Automatic merge failed, ...'Fredrik Kuivinen, Sep 13, 2005
  4. 3/5 Adjust git-merge-recursive.py for the new tool names.Fredrik Kuivinen, Sep 13, 2005
  5. 4/5 Use a temporary index file when we merge the common ancestors.Fredrik Kuivinen, Sep 13, 2005
  6. 5/5 Use the 'die' function where it is appropriate.Fredrik Kuivinen, Sep 13, 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.