From: Sverre Hvammen Johansen <hvammen+git@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH/Test] Build in merge is broken
Date: Sun, 13 Jul 2008 08:13:55 +0000 (UTC) [thread overview]
Message-ID: <loom.20080713T073129-112@post.gmane.org> (raw)
This test case shows breakage of build in merge. This have been
bisected to 1c7b76be Build in merge.
---
Great that we now are introducing merge in C. Great job Miklos.
However, it is broken as this patch shows. This have been
bisected to 1c7b76be Build in merge.
The test case when run will record the parents that were asked for which is
fine. However, only c2 is recorded as a parent in the commit object. Both
c1 and c2 should have been recorded. The merge is otherwise working
correctly.
t/t7600-merge.sh | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/t/t7600-merge.sh b/t/t7600-merge.sh
index 16f4608..a96a497 100755
--- a/t/t7600-merge.sh
+++ b/t/t7600-merge.sh
@@ -465,4 +465,15 @@ test_expect_success 'merge log message' '
test_debug 'gitk --all'
+test_expect_success 'merge c1 with c0, c2, c0, and c1' '
+ git reset --hard c1 &&
+ git config branch.master.mergeoptions "" &&
+ test_tick &&
+ git merge c0 c2 c0 c1 &&
+ verify_merge file result.1-5 &&
+ verify_parents $c1 $c2
+'
+
+test_debug 'gitk --all'
+
test_done
--
1.5.5.54.gc6550
next reply other threads:[~2008-07-13 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 8:13 Sverre Hvammen Johansen [this message]
2008-07-13 12:41 ` [PATCH/Test] Build in merge is broken Miklos Vajna
2008-07-13 17:46 ` Miklos Vajna
2008-07-13 18:43 ` Miklos Vajna
2008-07-13 19:11 ` Junio C Hamano
2008-07-14 2:15 ` Sverre Hvammen Johansen
2008-07-14 2:53 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20080713T073129-112@post.gmane.org \
--to=hvammen+git@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox