From: Junio C Hamano <gitster@pobox•com>
To: Peter Krefting <peter@softwolves•pp.se>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>,
Johan Herland <johan@herland•net>,
Git mailing list <git@vger•kernel.org>
Subject: Re: Having Git follow symlinks
Date: Fri, 31 Jan 2014 09:23:15 -0800 [thread overview]
Message-ID: <xmqq38k4hxq4.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1401311052370.3993@ds9.cixit.se> (Peter Krefting's message of "Fri, 31 Jan 2014 10:56:41 +0100 (CET)")
Peter Krefting <peter@softwolves•pp.se> writes:
> ...if I have the time, maybe I can come up with a patch. There is
> already some hacks in the "core.symlinks" setting, so I guess it
> should be possible.
That is totally unrelated. The variable only says "on this platform
and/or filesystem, you cannot symlink(2), so instead create a
regular file with the symlink contents when checking out a symlink
blob". Most importantly, the variable does not change the fact that
symbolic links are explicitly tracked without dereferencing.
If you have, under a directory foo/, a symbolic link foo/bar that
points at "../baz", a directory foo/baz/, and you have a file at
foo/baz/hello:
1. "git add foo" and "git add foo/bar" will add foo/bar as a
symlink; and
2. "git add foo/bar/hello" is an error.
The variable does not have any interactions with the logic to make
sure 2. errors out correctly, so the presense of it does not imply
anything.
next prev parent reply other threads:[~2014-01-31 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 13:49 Having Git follow symlinks Peter Krefting
2014-01-28 14:47 ` Johan Herland
2014-01-30 9:01 ` Peter Krefting
2014-01-30 10:09 ` Christian Couder
2014-01-30 12:37 ` Matthieu Moy
2014-01-31 9:56 ` Peter Krefting
2014-01-31 13:20 ` Matthew Ruffalo
2014-01-31 17:23 ` Junio C Hamano [this message]
2014-01-31 17:56 ` Matthieu Moy
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=xmqq38k4hxq4.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=johan@herland$(echo .)net \
--cc=peter@softwolves$(echo .)pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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