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

[PATCH] t6021: add a new test for git-merge-resolve

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Jul 12, 2008, 18:42 UTC
Message-ID
<1215888130-3260-1-git-send-email-vmiklos@frugalware.org>

It should fail properly if there are multiple merge bases, but there were no test for this till now.

Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
---
 t/t6021-merge-criss-cross.sh |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/t/t6021-merge-criss-cross.sh b/t/t6021-merge-criss-cross.sh
index 0ab14a6..331b9b0 100755
--- a/t/t6021-merge-criss-cross.sh
+++ b/t/t6021-merge-criss-cross.sh
@@ -89,4 +89,8 @@ EOF
 
 test_expect_success 'Criss-cross merge result' 'cmp file file-expect'
 
+test_expect_success 'Criss-cross merge fails (-s resolve)' \
+'git reset --hard A^ &&
+test_must_fail git merge -s resolve -m "final merge" B'
+
 test_done
-- 
1.5.6.2.450.g8d367.dirty
Next: Miklos Vajna
Message 1 of 2 in “t6021: add a new test for git-merge-resolve”
  1. t6021: add a new test for git-merge-resolveMiklos Vajna, Jul 12, 2008
  2. Add a new test for git-merge-resolveMiklos Vajna, Jul 12, 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.