From: Elijah Newren <newren@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Elijah Newren <newren@gmail.com>
Subject: [PATCH 1/2] t6031: Add a testcase covering multiple renames across a D/F conflict
Date: Tue, 17 Aug 2010 17:53:18 -0600 [thread overview]
Message-ID: <1282089199-17253-2-git-send-email-newren@gmail.com> (raw)
In-Reply-To: <1282089199-17253-1-git-send-email-newren@gmail.com>
Signed-off-by: Elijah Newren <newren@gmail.com>
---
t/t6031-merge-recursive.sh | 28 ++++++++++++++++++++++++++++
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/t/t6031-merge-recursive.sh b/t/t6031-merge-recursive.sh
index 8a3304f..aa235b9 100755
--- a/t/t6031-merge-recursive.sh
+++ b/t/t6031-merge-recursive.sh
@@ -57,4 +57,32 @@ test_expect_success FILEMODE 'verify executable bit on file' '
test -x file2
'
+test_expect_failure 'merging with triple rename across D/F conflict' '
+ git reset --hard HEAD &&
+ git checkout --orphan main &&
+ git rm -rf . &&
+
+ echo "just a file" > sub1 &&
+ mkdir -p sub2 &&
+ echo content > sub2/file1 &&
+ echo content > sub2/file2 &&
+ echo content > sub2/file3 &&
+ mkdir simple &&
+ echo base > simple/bar &&
+ git add -A &&
+ git commit -m base &&
+
+ git checkout -b other &&
+ echo more >> simple/bar &&
+ git commit -a -m changesimplefile &&
+
+ git checkout main &&
+ git rm sub1 &&
+ git mv sub2 sub1 &&
+ git commit -m changefiletodir &&
+
+ git merge other
+'
+
+
test_done
--
1.7.2.1.227.g086c8
next prev parent reply other threads:[~2010-08-17 23:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 23:53 [PATCH 0/2] Fix multiple file rename across D/F conflict Elijah Newren
2010-08-17 23:53 ` Elijah Newren [this message]
2010-08-17 23:53 ` [PATCH 2/2] merge-recursive: " Elijah Newren
2010-08-18 19:00 ` Junio C Hamano
2010-08-18 23:17 ` Junio C Hamano
2010-08-20 12:47 ` Elijah Newren
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=1282089199-17253-2-git-send-email-newren@gmail.com \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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;
as well as URLs for NNTP newsgroup(s).