From: James Pickens <james.e.pickens@intel.com>
To: git@vger.kernel.org, gitster@pobox.com
Cc: barvik@broadpark.no
Subject: More symlink/directory troubles
Date: Tue, 28 Jul 2009 15:13:16 -0700 [thread overview]
Message-ID: <1248819198-13921-1-git-send-email-james.e.pickens@intel.com> (raw)
This is a follow up to the original thread and patch at
http://article.gmane.org/gmane.comp.version-control.git/122297. There was
a bug report about problems when a directory is replaced with a symlink. I
said that the patch fixed the bug for me, but I didn't test thoroughly
enough, because it turns out there are 3 bugs, and the patch only fixed one
of them.
I am sending some test scripts to demonstrate the bugs in hopes of spurring
some activity here. I think the convention is to use test_expect_failure
for this sort of test, so that's what I did.
Unfortunately I have very little time in the next 2 weeks, so I probably
won't be able to do much more than send the tests, and fix them up if
necessary. In 2 weeks I can take a look at the C code, if it isn't already
fixed by then.
James
next reply other threads:[~2009-07-28 22:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 22:13 James Pickens [this message]
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 ` [PATCH 1/2] Demonstrate bugs " Michael J Gruber
2009-07-29 8:33 ` 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=1248819198-13921-1-git-send-email-james.e.pickens@intel.com \
--to=james.e.pickens@intel.com \
--cc=barvik@broadpark.no \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).