From: tarmigan+git@gmail.com
To: "Junio C Hamano" <junkio@cox.net>, git@vger.kernel.org
Subject: possible regression (or me abusing git) in v1.5.5
Date: Fri, 11 Apr 2008 12:21:41 -0700 [thread overview]
Message-ID: <905315640804111221k53dd7063sae5710ed690114f0@mail.gmail.com> (raw)
Hello,
After upgrading to v1.5.5, I noticed a change in the way that git
treats symbolic links.
Git will follow symbolic links to directories when they were added as follows
$ git init
$ mkdir foo
$ touch foo/bar
$ ln -s foo foo1
$ git add foo1/
# Note the trailing slash above.
In v1.5.5 (but not v1.5.4.5 and earlier),
$ git add -u
will remove foo1/bar from the index.
I have bisected this down to f58dbf (diff-files: careful when
inspecting work tree items).
The ability for git to follow links (instead of recording them) was a
useful feature for me, but I may have been abusing this "feature". If
that is the consensus, it might make sense to have
$ git add foo1
and
$ git add foo1/
behave the same way?
Thanks,
Tarmigan
next reply other threads:[~2008-04-11 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 19:21 tarmigan+git [this message]
2008-04-11 21:06 ` possible regression (or me abusing git) in v1.5.5 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=905315640804111221k53dd7063sae5710ed690114f0@mail.gmail.com \
--to=tarmigan+git@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).