Re: Git doesn't support symlinks

From: Daniel Malendez <dmalendez@googlemail.com>
Date: Mar 26, 2020, 00:37 UTC
Message-ID: <F9453040-2E7D-4CAB-AA7F-0C6C04E2FC99@googlemail.com>
In-Reply-To: <D3B355BB-BB09-4AA7-8D8A-58B61529D617@googlemail.com>

Thanks for your feedback!

Show 5 quoted lines

> On Mar 25, 2020, at 8:23 PM, Bryan Turner <bturner@atlassian.com> wrote:
> 
> This didn't add the same thing. What does a "git status" show at this
> point? I'd expect it would show "Versions/Current/Headers/interior.h"
> as added to the index, not "Headers/interior.h".

$ git add .
$ git status
Changes to be committed:
  (use "git rm --cached <file>..." to unstage)
	new file:   Foo.framework/Headers
	new file:   Foo.framework/Versions/A/Headers/Interior.h

Show 5 quoted lines

> It doesn't necessarily seem like a bug, to me; more like a case where
> Git could potentially be "smarter" to try and determine that, while
> "Headers/interior.h" is beyond a symlink, the target of that symlink
> is still in the repository. (Versions/Current _is_ in the same
> repository, right?)

Agree, makes sense!

I think what happens here is that `git add .` adds the Foo.framework/Headers directory first, to circumvent this check failing here? https://github.com/git/git/blob/master/pathspec.c#L596 Whereas a single “git add path/to/file” would fail here