From: Jeff King <peff@peff.net>
To: shawn wilson <ag4ve.us@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, git@vger.kernel.org
Subject: Re: change symlink
Date: Wed, 31 Oct 2012 08:05:05 -0400 [thread overview]
Message-ID: <20121031120505.GD30879@sigill.intra.peff.net> (raw)
In-Reply-To: <CAH_OBidmrJsmw1QQ2WONieA1EQmS_Y4WJ8Mu2Mh90tEPU0uWgw@mail.gmail.com>
On Tue, Oct 30, 2012 at 10:22:04PM +0000, shawn wilson wrote:
> On Tue, Oct 30, 2012 at 10:09 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> > shawn wilson <ag4ve.us@gmail.com> writes:
> >
> >> and once it's added, status says:
> >> # renamed: t2 -> t2/one/test
> >>
> >> that's not exactly true, but...
> >
> > What's wrong with it? Both files have the same contents, which is the
> > link target for symlinks.
> >
>
> ok, you're right about that (another test where i changed where the
> symlink pointed):
> # deleted: test
> # new file: test/one/t3
>
>
> however (what got me started wondering about this and a point i forgot
> about) - t2/one/test doesn't show up under 'untracked files' in in
> status that scenario. shouldn't it?
Yes, I think that is a bug.
My guess is that the presence of "test" in the index fools us from
descending into the directory. And indeed, if you try "git status
-uall", you will see the untracked file. So it is something with the
directory traversal cutoff in the regular "-unormal" mode.
-Peff
next prev parent reply other threads:[~2012-10-31 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 21:07 change symlink shawn wilson
2012-10-30 21:19 ` Andreas Schwab
2012-10-30 21:24 ` shawn wilson
2012-10-30 21:35 ` Andreas Schwab
2012-10-30 21:42 ` shawn wilson
2012-10-30 21:50 ` Andreas Schwab
2012-10-30 22:03 ` shawn wilson
2012-10-30 22:09 ` Andreas Schwab
2012-10-30 22:22 ` shawn wilson
2012-10-31 12:05 ` Jeff King [this message]
2012-10-31 12:30 ` Jeff King
2012-10-31 13:44 ` Jeff King
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=20121031120505.GD30879@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=ag4ve.us@gmail.com \
--cc=git@vger.kernel.org \
--cc=schwab@linux-m68k.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).