From: Mikhail Filippov <mikhail@filippov.me>
To: git@vger.kernel.org
Cc: Mikhail Filippov <mikhail@filippov.me>
Subject: [PATCH] Do not record unstaged deleted file upon recursive merge if file was moved outside of working tree with enabled sparse-checkout.
Date: Sun, 11 Sep 2016 23:25:05 +0300 [thread overview]
Message-ID: <1473625505-7641-1-git-send-email-mikhail@filippov.me> (raw)
---
merge-recursive.c | 9 +++++---
t/t6042-merge-rename-corner-cases.sh | 42 ++++++++++++++++++++++++++++++++++++
2 files changed, 48 insertions(+), 3 deletions(-)
diff --git a/merge-recursive.c b/merge-recursive.c
index e349126..25dc701 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -1724,9 +1724,12 @@ static int merge_content(struct merge_options *o,
*/
path_renamed_outside_HEAD = !path2 || !strcmp(path, path2);
if (!path_renamed_outside_HEAD) {
- add_cacheinfo(o, mfi.mode, &mfi.oid, path,
- 0, (!o->call_depth), 0);
- return mfi.clean;
+ struct stat st;
+ if (lstat(path, &st) == 0) {
+ add_cacheinfo(o, mfi.mode, &mfi.oid, path,
+ 0, (!o->call_depth), 0);
+ return mfi.clean;
+ }
}
} else
output(o, 2, _("Auto-merging %s"), path);
diff --git a/t/t6042-merge-rename-corner-cases.sh b/t/t6042-merge-rename-corner-cases.sh
index 411550d..2073e49 100755
--- a/t/t6042-merge-rename-corner-cases.sh
+++ b/t/t6042-merge-rename-corner-cases.sh
@@ -575,4 +575,46 @@ test_expect_success 'rename/rename/add-dest merge still knows about conflicting
test ! -f c
'
+test_expect_success 'move file/sparse-checkout/merge should not delete moved file' '
+ git rm -rf . &&
+ git clean -fdqx &&
+ rm -rf .git &&
+ git init &&
+
+ echo output >.gitignore &&
+ echo .gitignore >>.gitignore &&
+
+ echo b1 >b1 &&
+ git add b1 &&
+ git commit -m b1 &&
+
+ mkdir excluded &&
+ echo problem >excluded/to-be-moved.txt &&
+ git add excluded/to-be-moved.txt &&
+ git commit -m to-be-moved &&
+ git tag split_point &&
+
+ echo b2 >b2 &&
+ git add b2 &&
+ git commit -m b2 &&
+ git tag b2 &&
+
+ git reset --hard split_point &&
+
+ git mv excluded/to-be-moved.txt excluded/moved.txt &&
+ git commit -m move &&
+ git tag b1 &&
+
+ git config core.sparsecheckout true &&
+ echo "/*" >.git/info/sparse-checkout &&
+ echo "!excluded/" >>.git/info/sparse-checkout &&
+ git read-tree -mu HEAD &&
+
+ git merge -m merge b2 &&
+
+ git status >output &&
+ cp output /tmp/a &&
+ test_i18ngrep "nothing to commit" output
+'
+
test_done
--
2.7.4 (Apple Git-66)
next reply other threads:[~2016-09-11 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 20:25 Mikhail Filippov [this message]
2016-09-11 23:24 ` [PATCH] Do not record unstaged deleted file upon recursive merge if file was moved outside of working tree with enabled sparse-checkout Junio C Hamano
2016-09-12 8:38 ` Mikhail Filippov
2016-09-12 11:07 ` Mikhail Filippov
-- strict thread matches above, loose matches on Subject: below --
2016-09-12 11:24 Mikhail Filippov
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473625505-7641-1-git-send-email-mikhail@filippov.me \
--to=mikhail@filippov.me \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).