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

[PATCH 4/4] Add a second testcase for handling invalid strategies in git-merge

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Jul 29, 2008, 23:17 UTC
Message-ID
<f8e5afe347c194013ffd104b196a19a37d762f9b.1217372486.git.vmiklos@frugalware.org>
In-Reply-To
<ee13073cd83ff4a3cffb926b21cc54583e67f869.1217372486.git.vmiklos@frugalware.org>

This one tests '-s index' which is interesting because git-merge-index is an existing git command but it is not a valid strategy.

Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
---
 t/t7600-merge.sh |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/t/t7600-merge.sh b/t/t7600-merge.sh
index 5eeb6c2..0329aee 100755
--- a/t/t7600-merge.sh
+++ b/t/t7600-merge.sh
@@ -230,6 +230,10 @@ test_expect_success 'test option parsing' '
 	test_must_fail git merge
 '
 
+test_expect_success 'reject non-strategy with a git-merge-foo name' '
+	test_must_fail git merge -s index c1
+'
+
 test_expect_success 'merge c0 with c1' '
 	git reset --hard c0 &&
 	git merge c1 &&
-- 
1.6.0.rc0.14.g95f8.dirty
Previous: Miklos VajnaNext: Junio C Hamano
Message 5 of 10 in “Allow custom merge strategies, take 4”
  1. 0/4 Allow custom merge strategies, take 4Miklos Vajna, Jul 29, 2008
  2. 1/4 builtin-help: make some internal functions available to other builtinsMiklos Vajna, Jul 29, 2008
  3. 2/4 builtin-merge: allow using a custom strategyMiklos Vajna, Jul 29, 2008
  4. 3/4 Add a new test for using a custom merge strategyMiklos Vajna, Jul 29, 2008
  5. 4/4 Add a second testcase for handling invalid strategies in git-mergeMiklos Vajna, Jul 29, 2008
  6. Junio C HamanoJul 29, 2008
  7. Miklos VajnaJul 30, 2008
  8. Junio C HamanoJul 29, 2008
  9. Miklos VajnaJul 30, 2008
  10. Junio C HamanoJul 30, 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.