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

[PATCH] New test for preserve merges and squash

From
JSJörg Sommer <joerg@alea.gnuu.de>
Date
Mar 20, 2008, 00:03 UTC
Message-ID
<1205971432-12641-1-git-send-email-joerg@alea.gnuu.de>
Signed-off-by: Jörg Sommer <joerg@alea.gnuu.de>
---
 t/t3404-rebase-interactive.sh |   20 ++++++++++++++++++++
 1 files changed, 20 insertions(+), 0 deletions(-)

The current version of git fails this test. I think it's a bug, because the patch is what I expect to happen. Or am I wrong?

diff --git a/t/t3404-rebase-interactive.sh b/t/t3404-rebase-interactive.sh
index 62e65d7..05f3828 100755
--- a/t/t3404-rebase-interactive.sh
+++ b/t/t3404-rebase-interactive.sh
@@ -213,6 +213,26 @@ test_expect_success 'preserve merges with -p' '
 	test $(git show HEAD~2:file1) = B
 '
 
+# This test uses to-be-preserved from the test 'preserve merges with -p'
+test_expect_success 'squash and preserve merges' '
+	test_tick &&
+	git checkout -b squash-and-preserve-merges master &&
+	echo A > file1 &&
+	git commit -m SaPM-1 file1 &&
+	echo B > file1 &&
+	git commit -m SaPM-2 file1 &&
+	git merge to-be-preserved &&
+	echo C > file1 &&
+	git commit -m SaPM-3 file1 &&
+
+        EXPECT_COUNT=4 FAKE_LINES="1 2 squash 4 3" \
+          git rebase -i -p --onto branch1 master &&
+	test $(git rev-parse HEAD^2) = $(git rev-parse to-be-preserved) &&
+	test $(git rev-parse HEAD~3) = $(git rev-parse branch1) &&
+	test $(git show HEAD:file1) = C &&
+	test $(git show HEAD~2:file1) = A
+'
+
 test_expect_success '--continue tries to commit' '
 	test_tick &&
 	! git rebase -i --onto new-branch1 HEAD^ &&
-- 
1.5.4.4
Next: Junio C Hamano
Message 1 of 8 in “New test for preserve merges and squash”
  1. New test for preserve merges and squashJörg Sommer, Mar 20, 2008
  2. Junio C HamanoMar 20, 2008
  3. Jörg SommerMar 20, 2008
  4. Johannes SchindelinMar 20, 2008
  5. New test for rebase with preserve merges and squashJörg Sommer, Mar 20, 2008
  6. Johannes SchindelinMar 20, 2008
  7. Why rebase with preserve merges asks for merged commitsJörg Sommer, Mar 21, 2008
  8. Johannes SchindelinMar 21, 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.