From: Ciaran <ciaranj@gmail.com>
To: git@vger.kernel.org, newren@gmail.com,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH RFC] Test for apparent regression of merging renamed files
Date: Mon, 2 May 2011 20:04:24 +0100 [thread overview]
Message-ID: <BANLkTimcRbuYzSp+MM-vsvxoWhAS8Jvo8Q@mail.gmail.com> (raw)
Provides a test to cover a case that appears to have been regressed out by:
b2c8c0a762745768e8fb249949801c1aed8f7c1d
At this point no tags contain the above commit, but 'master' does. I'm unsure
what is causing the issue, but can see discussion about this fix here:
http://git.661346.n2.nabble.com/BUG-merge-recursive-triggered-quot-BUG-quot-td6179353.html
Providing a patch to demonstrate the issue and spark discussion.
---
Whilst working up a patch for my 'whitespace ignorant rename
detection' ( http://git.661346.n2.nabble.com/PATCH-RFC-Rename-detection-and-whitespace-td6288524.html
) I was unable to get my tests working, turns out that something that
used to work for me, no longer does in master's HEAD.
I don't really understand the fault so I'm throwing it to the list in
the hope that someone brighter than me can take it on (I've
CC'd the signoff-s to that end! :) Sorry!
t/t9801-merge-rename.sh | 41 +++++++++++++++++++++++++++++++++++++++++
1 files changed, 41 insertions(+), 0 deletions(-)
create mode 100755 t/t9801-merge-rename.sh
diff --git a/t/t9801-merge-rename.sh b/t/t9801-merge-rename.sh
new file mode 100755
index 0000000..363911f
--- /dev/null
+++ b/t/t9801-merge-rename.sh
@@ -0,0 +1,41 @@
+#!/bin/sh
+
+test_description='Test for rename merge regression'
+
+. ./test-lib.sh
+
+write_out_files() {
+cat > noformatting.txt << EOF
+if(true){
+// Meaningless
+}
+EOF
+
+cat > formatting.txt << EOF
+ if ( true ) {
+ // Meaningless
+ }
+EOF
+}
+
+# Test the case where a rename happens in one branch and
+# a whitespace change occurs in a different branch. The rename
+# change should apply to the whitespace modified file
+test_expect_success setup '
+ write_out_files &&
+ git add formatting.txt &&
+
+ test_tick &&
+ git commit -m Initial &&
+ git checkout -b rename_branch &&
+ git mv formatting.txt formatting_renamed.txt &&
+ git commit -m Rename &&
+ git checkout master &&
+ rm formatting.txt &&
+ mv noformatting.txt formatting.txt &&
+ git commit -a -m Reformat
+'
+test_expect_success 'merge' '
+ git merge rename_branch
+'
+test_done
--
1.7.4.1
next reply other threads:[~2011-05-02 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 19:04 Ciaran [this message]
2011-05-03 19:15 ` [PATCH RFC] Test for apparent regression of merging renamed files Ciaran
2011-05-04 2:18 ` 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=BANLkTimcRbuYzSp+MM-vsvxoWhAS8Jvo8Q@mail.gmail.com \
--to=ciaranj@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.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).