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

[PATCH 5/5] Add a new test for using a custom merge strategy

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Jul 29, 2008, 15:25 UTC
Message-ID
<3c77f8dd8b229bb08b5bc0b6a8efd7359df5ecc9.1217344803.git.vmiklos@frugalware.org>
In-Reply-To
<722d66a5a897b694f374aa96bd58aff01a2a5932.1217344803.git.vmiklos@frugalware.org>

Testing is done by creating a simple git-merge-theirs strategy which is the opposite of ours. Using this in real merges is not recommended but it's perfect for our testing needs.

Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
---
 t/t7606-merge-custom.sh |   46 ++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 46 insertions(+), 0 deletions(-)
 create mode 100755 t/t7606-merge-custom.sh
diff --git a/t/t7606-merge-custom.sh b/t/t7606-merge-custom.sh
new file mode 100755
index 0000000..13e8ff5
--- /dev/null
+++ b/t/t7606-merge-custom.sh
@@ -0,0 +1,46 @@
+#!/bin/sh
+
+test_description='git-merge
+
+Testing a custom strategy.'
+
+. ./test-lib.sh
+
+cat > git-merge-theirs << EOF
+#!/bin/sh
+eval git read-tree --reset -u \\\$\$#
+EOF
+chmod +x git-merge-theirs
+PATH=.:$PATH
+export PATH
+
+test_expect_success 'setup' '
+	echo c0 > c0.c &&
+	git add c0.c &&
+	git commit -m c0 &&
+	git tag c0 &&
+	echo c1 > c1.c &&
+	git add c1.c &&
+	git commit -m c1 &&
+	git tag c1 &&
+	git reset --hard c0 &&
+	echo c2 > c2.c &&
+	git add c2.c &&
+	git commit -m c2 &&
+	git tag c2
+'
+
+test_expect_success 'merge c2 with a custom strategy' '
+	git reset --hard c1 &&
+	git merge -s theirs c2 &&
+	test "$(git rev-parse c1)" != "$(git rev-parse HEAD)" &&
+	test "$(git rev-parse c1)" = "$(git rev-parse HEAD^1)" &&
+	test "$(git rev-parse c2)" = "$(git rev-parse HEAD^2)" &&
+	test "$(git rev-parse c2^{tree})" = "$(git rev-parse HEAD^{tree})" &&
+	git diff --exit-code &&
+	test -f c0.c &&
+	test ! -f c1.c &&
+	test -f c2.c
+'
+
+test_done
-- 
1.6.0.rc0.14.g95f8.dirty
Previous: Miklos VajnaNext: Junio C Hamano
Message 6 of 9 in “Allow custom merge strategies, take 3”
  1. 0/5 Allow custom merge strategies, take 3Miklos Vajna, Jul 29, 2008
  2. 1/5 builtin-help: make is_git_command() usable outside builtin-helpMiklos Vajna, Jul 29, 2008
  3. 2/5 builtin-help: make list_commands() a bit more genericMiklos Vajna, Jul 29, 2008
  4. 3/5 builtin-help: make it possible to exclude some commands in list_commands()Miklos Vajna, Jul 29, 2008
  5. 4/5 builtin-merge: allow using a custom strategyMiklos Vajna, Jul 29, 2008
  6. 5/5 Add a new test for using a custom merge strategyMiklos Vajna, Jul 29, 2008
  7. Junio C HamanoJul 29, 2008
  8. Junio C HamanoJul 29, 2008
  9. 3/5 builtin-help: make it possible to exclude some commands in list_commands()Miklos Vajna, Jul 29, 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.