From: newren@gmail.com
To: git@vger.kernel.org
Cc: Johannes.Schindelin@gmx.de, vmiklos@frugalware.org,
gitster@pobox.com, spearce@spearce.org,
Elijah Newren <newren@gmail.com>
Subject: [PATCH 5/5] fast-import: Handle directories changing into symlinks
Date: Mon, 28 Jun 2010 19:12:16 -0600 [thread overview]
Message-ID: <1277773936-12412-6-git-send-email-newren@gmail.com> (raw)
In-Reply-To: <1277773936-12412-1-git-send-email-newren@gmail.com>
From: Elijah Newren <newren@gmail.com>
Signed-off-by: Elijah Newren <newren@gmail.com>
---
This is a resend of an earlier patch. Since the previous one wasn't
reviewed and didn't make it to pu, I decided to resend it along with the
merge-recursive directory/symlink conflict fixes as part of a patch series.
fast-import.c | 5 +++++
t/t9350-fast-export.sh | 2 +-
2 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/fast-import.c b/fast-import.c
index 1e5d66e..9a2ecc8 100644
--- a/fast-import.c
+++ b/fast-import.c
@@ -1528,6 +1528,11 @@ static int tree_content_remove(
for (i = 0; i < t->entry_count; i++) {
e = t->entries[i];
if (e->name->str_len == n && !strncmp(p, e->name->str_dat, n)) {
+ if (slash1 && S_ISLNK(e->versions[1].mode))
+ /* p was already removed by an earlier change
+ * of a parent directory to a symlink.
+ */
+ return 1;
if (!slash1 || !S_ISDIR(e->versions[1].mode))
goto del_entry;
if (!e->tree)
diff --git a/t/t9350-fast-export.sh b/t/t9350-fast-export.sh
index 69179c6..1ee1461 100755
--- a/t/t9350-fast-export.sh
+++ b/t/t9350-fast-export.sh
@@ -376,7 +376,7 @@ test_expect_success 'tree_tag-obj' 'git fast-export tree_tag-obj'
test_expect_success 'tag-obj_tag' 'git fast-export tag-obj_tag'
test_expect_success 'tag-obj_tag-obj' 'git fast-export tag-obj_tag-obj'
-test_expect_failure 'directory becomes symlink' '
+test_expect_success 'directory becomes symlink' '
git init dirtosymlink &&
git init result &&
(
--
1.7.2.rc0.212.g0c601
prev parent reply other threads:[~2010-06-29 1:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 1:12 [PATCH 0/5] D/F conflict fixes newren
2010-06-29 1:12 ` [PATCH 1/5] Add additional testcases for D/F conflicts newren
2010-06-29 1:12 ` [PATCH 2/5] Add another rename + D/F conflict testcase newren
2010-06-29 8:49 ` Alexander Gladysh
2010-06-29 1:12 ` [PATCH 3/5] merge-recursive: Fix D/F conflicts newren
2010-06-29 1:12 ` [PATCH 4/5] merge_recursive: Fix renames across paths below " newren
2010-06-29 7:54 ` Miklos Vajna
2010-06-29 12:52 ` Elijah Newren
2010-06-29 13:36 ` Alex Riesen
2010-06-29 15:55 ` Elijah Newren
2010-06-29 22:33 ` Miklos Vajna
2010-06-30 6:53 ` Alex Riesen
2010-06-29 1:12 ` newren [this message]
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=1277773936-12412-6-git-send-email-newren@gmail.com \
--to=newren@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
--cc=vmiklos@frugalware.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).