From: Michael J Gruber <git@drmicha.warpmail.net>
To: James Pickens <james.e.pickens@intel.com>
Cc: git@vger.kernel.org, gitster@pobox.com, barvik@broadpark.no
Subject: Re: [PATCH 1/2] Demonstrate bugs when a directory is replaced with a symlink.
Date: Wed, 29 Jul 2009 10:19:54 +0200 [thread overview]
Message-ID: <4A70062A.4040008@drmicha.warpmail.net> (raw)
In-Reply-To: <1248819198-13921-2-git-send-email-james.e.pickens@intel.com>
James Pickens venit, vidit, dixit 29.07.2009 00:13:
> This test creates two directories, a/b and a/b-2, then replaces a/b with
> a symlink to a/b-2, then merges that change into another branch that
> contains an unrelated change.
>
> There are two bugs:
> 1. 'git checkout' wrongly deletes work tree file a/b-2/d.
> 2. 'git merge' wrongly deletes work tree file a/b-2/d.
>
> Signed-off-by: James Pickens <james.e.pickens@intel.com>
> ---
> t/t6035-merge-dir-to-symlink.sh | 32 ++++++++++++++++++++++++++++++++
> 1 files changed, 32 insertions(+), 0 deletions(-)
> create mode 100755 t/t6035-merge-dir-to-symlink.sh
>
> diff --git a/t/t6035-merge-dir-to-symlink.sh b/t/t6035-merge-dir-to-symlink.sh
> new file mode 100755
> index 0000000..926c8ed
> --- /dev/null
> +++ b/t/t6035-merge-dir-to-symlink.sh
> @@ -0,0 +1,32 @@
> +#!/bin/sh
> +
> +test_description='merging when a directory was replaced with a symlink'
> +. ./test-lib.sh
> +
> +test_expect_success setup '
> + mkdir -p a/b/c a/b-2/c &&
> + > a/b/c/d &&
> + > a/b-2/c/d &&
> + > a/x &&
> + git add -A &&
> + git commit -m base &&
> + rm -rf a/b &&
> + ln -s b-2 a/b &&
> + git add -A &&
> + git commit -m "dir to symlink"
> +'
> +
> +test_expect_failure 'checkout should not delete a/b-2/c/d' '
> + git checkout -b temp HEAD^ &&
> + test -f a/b-2/c/d
> +'
> +
> +test_expect_failure 'merge should not delete a/b-2/c/d' '
> + echo x > a/x &&
> + git add a/x &&
> + git commit -m x &&
> + git merge master &&
> + test -f a/b-2/c/d
> +'
> +
> +test_done
Isn't the failure of the second test caused by that of the first one?
a/b-2/c/d is gone from the worktree, and master does not touch it, so
the merge leaves the worktree version (non-existent) as is.
Michael
next prev parent reply other threads:[~2009-07-29 8:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 22:13 More symlink/directory troubles James Pickens
2009-07-28 22:13 ` [PATCH 1/2] Demonstrate bugs when a directory is replaced with a symlink James Pickens
2009-07-28 22:13 ` [PATCH 2/2] Demonstrate merge failure " James Pickens
2009-07-29 8:29 ` Michael J Gruber
2009-07-29 16:39 ` Pickens, James E
2009-07-29 8:19 ` Michael J Gruber [this message]
2009-07-29 8:33 ` [PATCH 1/2] Demonstrate bugs " Junio C Hamano
2009-07-29 16:57 ` Pickens, James E
2009-07-29 17:48 ` [PATCH v2] " Pickens, James E
2009-07-29 18:31 ` Junio C Hamano
2009-07-29 21:02 ` [PATCH v3] " Pickens, James E
2009-07-29 22:08 ` Linus Torvalds
2009-07-29 22:44 ` Junio C Hamano
2009-07-29 23:01 ` Kjetil Barvik
2009-07-29 23:58 ` Linus Torvalds
2009-07-30 1:06 ` Linus Torvalds
2009-07-30 3:26 ` Junio C Hamano
2009-07-30 6:05 ` Junio C Hamano
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=4A70062A.4040008@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=barvik@broadpark.no \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=james.e.pickens@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.