Re: symlinked working tree gotcha

[Joey Hess <joey@kitenet.net>]

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

Junio C Hamano wrote:
> Two 'foo's makes it confusing to read so let's rephrase.
> 
> Given this structure:
> 
>     /tmp/foo/
>     /tmp/foo/.git/
>     /tmp/foo/hello
>     /tmp/sym@ -> foo
> 
> when you refer to /tmp/sym/hello where $(/bin/pwd) is /tmp/foo, should it
> be considered to be within the bounds of the working tree that is governed
> by your current $GIT_DIR (which is ".git")?

Hmm, my /bin/pwd does not return "/tmp/foo" when I've cd'd to "/tmp/sym".

> The answer is "perhaps yes, ideally speaking, but does it really matter in
> practice, or is it just nice to have?".

FWIW, my motivation for using the absolute path was that I wanted to
always add $GIT_WORK_TREE/hello, but the add could be run when in a
subdirectory of the repository, so "git add hello" might not add the
right file.

-- 
see shy jo

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]