From: Vitor Antunes <vitor.hda@gmail.com>
To: git@vger.kernel.org
Cc: Vitor Antunes <vitor.hda@gmail.com>
Subject: [PATCH V2 2/2] git-p4: Fix copy detection test
Date: Sat, 28 Mar 2015 00:03:03 +0000 [thread overview]
Message-ID: <1427500983-8802-3-git-send-email-vitor.hda@gmail.com> (raw)
In-Reply-To: <1427500983-8802-1-git-send-email-vitor.hda@gmail.com>
File file11 is copied from file2 and diff-tree correctly reports this file as
its the source. But it is possible that the diff-tree algorithm detects file10,
which was also copied from file2, as the origin of the new file.
This fix uses a case statement to support both files as the source of file11, as
was done in other tests in this file.
Signed-off-by: Vitor Antunes <vitor.hda@gmail.com>
---
t/t9814-git-p4-rename.sh | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/t/t9814-git-p4-rename.sh b/t/t9814-git-p4-rename.sh
index efae143..8b9c295 100755
--- a/t/t9814-git-p4-rename.sh
+++ b/t/t9814-git-p4-rename.sh
@@ -163,7 +163,10 @@ test_expect_success 'detect copies' '
git commit -a -m "Copy file2 to file11" &&
git diff-tree -r -C --find-copies-harder HEAD &&
src=$(git diff-tree -r -C --find-copies-harder HEAD | sed 1d | cut -f2) &&
- test "$src" = file10 &&
+ case "$src" in
+ file2 | file10) : ;; # happy
+ *) false ;; # not
+ esac &&
git config git-p4.detectCopiesHarder true &&
git p4 submit &&
p4 filelog //depot/file11 &&
--
1.7.10.4
next prev parent reply other threads:[~2015-03-28 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 0:03 [PATCH V2 0/2] git-p4: Small updates to test cases Vitor Antunes
2015-03-28 0:03 ` [PATCH V2 1/2] git-p4: Make rename test case runnable under dash Vitor Antunes
2015-03-28 0:03 ` Vitor Antunes [this message]
2015-03-28 16:07 ` [PATCH V2 0/2] git-p4: Small updates to test cases 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=1427500983-8802-3-git-send-email-vitor.hda@gmail.com \
--to=vitor.hda@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;
as well as URLs for NNTP newsgroup(s).