From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Gerrit Pape" <pape@smarden.org>,
git@vger.kernel.org, "Rémi Vanicat" <vanicat@debian.org>
Subject: [PATCH 2/2] Add tests for cherry-pick d/f conflict which should be none
Date: Tue, 17 Jul 2007 18:14:48 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707171814330.14781@racer.site> (raw)
In-Reply-To: <7v8x9q1x5t.fsf@assigned-by-dhcp.cox.net>
This tests that we fixed the problem when a directory was renamed,
and a symlink was added in its place (or for that matter, if
the type changed in one branch, and the name in another).
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
The last test checks that also a file/symlink conflict does
not break cherry-pick, if one side had a clean rename.
t/t3502-cherry-pick.sh | 43 +++++++++++++++++++++++++++++++++++++++++++
1 files changed, 43 insertions(+), 0 deletions(-)
create mode 100755 t/t3502-cherry-pick.sh
diff --git a/t/t3502-cherry-pick.sh b/t/t3502-cherry-pick.sh
new file mode 100755
index 0000000..9921de5
--- /dev/null
+++ b/t/t3502-cherry-pick.sh
@@ -0,0 +1,43 @@
+#!/bin/sh
+
+test_description='test cherry-pick'
+
+. ./test-lib.sh
+
+test_expect_success setup '
+ echo foo > file &&
+ ln -s dangling link &&
+ git add file link &&
+ test_tick &&
+ git commit -m foo &&
+ git checkout -b branch &&
+ git rm link &&
+ test_tick &&
+ git commit -m "remove link" &&
+ mkdir link &&
+ echo bar > link/file &&
+ git add link/file &&
+ test_tick &&
+ git commit -m "add dir" &&
+ echo bar > file &&
+ git commit -m "change file" file &&
+ git checkout master
+'
+
+test_expect_success 'cherry-pick ignores unrelated dir/symlink conflict' '
+ git cherry-pick branch
+'
+
+test_expect_success 'cherry-pick ignores unrelated file/symlink conflict' '
+ git checkout -b branch2 master^ &&
+ git rm link &&
+ test_tick &&
+ git commit -m "remove link" &&
+ : > link &&
+ git add link &&
+ test_tick &&
+ git commit -m "add file" &&
+ git cherry-pick master
+'
+
+test_done
--
1.5.3.rc1.16.g9d6f-dirty
next prev parent reply other threads:[~2007-07-17 17:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070405071615.2915.6837.reportbug@acer>
[not found] ` <20070607074357.27760.qmail@69aef7b888effd.315fe32.mid.smarden.org>
[not found] ` <6b8a91420706070252y3fd581a3w427d91e5b982d29d@mail.gmail.com>
2007-06-13 9:16 ` unexpected git-cherry-pick conflict Gerrit Pape
2007-06-13 12:58 ` Johannes Schindelin
2007-06-13 13:43 ` Gerrit Pape
2007-06-13 14:43 ` Johannes Schindelin
2007-06-25 7:18 ` Gerrit Pape
2007-06-25 7:55 ` Johannes Schindelin
2007-07-07 20:58 ` Johannes Schindelin
2007-12-21 10:37 ` Gerrit Pape
2007-12-22 8:20 ` Junio C Hamano
2007-07-08 0:52 ` [PATCH] merge-tree: sometimes, d/f conflict is not an issue Johannes Schindelin
2007-07-08 1:31 ` Junio C Hamano
2007-07-08 2:00 ` Johannes Schindelin
2007-07-08 2:18 ` Johannes Schindelin
2007-07-08 4:35 ` Johannes Schindelin
2007-07-08 5:50 ` Junio C Hamano
2007-07-08 6:14 ` Junio C Hamano
2007-07-08 13:16 ` Johannes Schindelin
2007-07-08 20:02 ` Junio C Hamano
2007-07-09 15:06 ` merge-one-file, was " Johannes Schindelin
2007-07-17 17:13 ` [PATCH 1/2] merge-recursive: " Johannes Schindelin
2007-08-08 14:39 ` Gerrit Pape
2007-07-17 17:14 ` Johannes Schindelin [this message]
2007-07-08 12:53 ` [PATCH] merge-tree: " Johannes Schindelin
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=Pine.LNX.4.64.0707171814330.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pape@smarden.org \
--cc=vanicat@debian.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).