From: newren@gmail.com
To: git@vger.kernel.org
Cc: gitster@pobox.com, spearce@spearce.org, agladysh@gmail.com,
Elijah Newren <newren@gmail.com>
Subject: [PATCHv3 2/6] Add a rename + D/F conflict testcase
Date: Tue, 6 Jul 2010 23:20:30 -0600 [thread overview]
Message-ID: <1278480034-22939-3-git-send-email-newren@gmail.com> (raw)
In-Reply-To: <1278480034-22939-1-git-send-email-newren@gmail.com>
From: Alexander Gladysh <agladysh@gmail.com>
This is a simple testcase where both sides of the rename are paths involved
in (separate) D/F merge conflicts
Signed-off-by: Alexander Gladysh <agladysh@gmail.com>
Signed-off-by: Elijah Newren <newren@gmail.com>
---
Copying my additional comments from round 2:
As noted previously this is simply a testcase Alexander sent to the
list on March 8 which I'm submitting in the form of a testsuite
addition. He's happy to have his testcase added to the testsuite
and/or even submit it himself if that makes more sense -- just let
us know what is wanted. I'm less familiar with format-patch and am;
hopefully this submission comes across with him recorded as the
author.
t/t3508-cherry-pick-merge-df.sh | 34 ++++++++++++++++++++++++++++++++++
1 files changed, 34 insertions(+), 0 deletions(-)
create mode 100755 t/t3508-cherry-pick-merge-df.sh
diff --git a/t/t3508-cherry-pick-merge-df.sh b/t/t3508-cherry-pick-merge-df.sh
new file mode 100755
index 0000000..646a56d
--- /dev/null
+++ b/t/t3508-cherry-pick-merge-df.sh
@@ -0,0 +1,34 @@
+#!/bin/sh
+
+test_description='Test cherry-pick with directory/file conflicts'
+. ./test-lib.sh
+
+test_expect_success 'Setup rename across paths each below D/F conflicts' '
+ mkdir a &&
+ touch a/f &&
+ git add a &&
+ git commit -m "a" &&
+
+ mkdir b &&
+ ln -s ../a b/a &&
+ git add b &&
+ git commit -m "b" &&
+
+ git checkout -b branch &&
+ rm b/a &&
+ mv a b/ &&
+ ln -s b/a a &&
+ git add . &&
+ git commit -m "swap" &&
+
+ touch f1 &&
+ git add f1 &&
+ git commit -m "f1"
+'
+
+test_expect_failure 'Cherry-pick succeeds with rename across D/F conflicts' '
+ git checkout master &&
+ git cherry-pick branch
+'
+
+test_done
--
1.7.1.1.10.g2e807
next prev parent reply other threads:[~2010-07-07 5:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 5:20 [PATCHv3 0/6] D/F conflict fixes newren
2010-07-07 5:20 ` [PATCHv3 1/6] Add additional testcases for D/F conflicts newren
2010-07-07 21:25 ` Junio C Hamano
2010-07-08 3:07 ` Elijah Newren
2010-07-08 16:03 ` Junio C Hamano
2010-07-07 5:20 ` newren [this message]
2010-07-07 21:26 ` [PATCHv3 2/6] Add a rename + D/F conflict testcase Junio C Hamano
2010-07-08 5:04 ` Elijah Newren
2010-07-07 5:20 ` [PATCHv3 3/6] merge-recursive: Fix D/F conflicts newren
2010-07-07 21:40 ` Junio C Hamano
2010-07-08 4:34 ` Elijah Newren
2010-07-07 5:20 ` [PATCHv3 4/6] merge_recursive: Fix renames across paths below " newren
2010-07-07 5:20 ` [PATCHv3 5/6] fast-export: Fix output order of D/F changes newren
2010-07-07 21:40 ` Junio C Hamano
2010-07-08 4:36 ` Elijah Newren
2010-07-08 6:04 ` Junio C Hamano
2010-07-07 5:20 ` [PATCHv3 6/6] fast-import: Improve robustness when D->F changes provided in wrong order 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=1278480034-22939-3-git-send-email-newren@gmail.com \
--to=newren@gmail.com \
--cc=agladysh@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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).