git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: tarmigan+git@gmail.com
Cc: git@vger.kernel.org
Subject: Re: possible regression (or me abusing git) in v1.5.5
Date: Fri, 11 Apr 2008 14:06:28 -0700	[thread overview]
Message-ID: <7vbq4grtij.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <905315640804111221k53dd7063sae5710ed690114f0@mail.gmail.com> (tarmigan+git@gmail.com's message of "Fri, 11 Apr 2008 12:21:41 -0700")

tarmigan+git@gmail.com writes:

> 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/

In this step "git add" adds "foo1/bar", which is a bug that is shared
between 1.5.5 and previous versions.

Recent "git add -u" after that was taught to notice this bogosity (it
actually is git-diff-* family that was fixed), and fixes it.

      reply	other threads:[~2008-04-11 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 19:21 possible regression (or me abusing git) in v1.5.5 tarmigan+git
2008-04-11 21:06 ` Junio C Hamano [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=7vbq4grtij.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=tarmigan+git@gmail.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).