From: Junio C Hamano <junkio@cox.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Getting rid of symlinks in .git?
Date: Mon, 14 Nov 2005 18:22:37 -0800 [thread overview]
Message-ID: <7vhdaevedu.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <81b0412b0511110443x48415032k8ca40d999071e8a9@mail.gmail.com> (Alex Riesen's message of "Fri, 11 Nov 2005 13:43:18 +0100")
Alex Riesen <raa.lkml@gmail.com> writes:
> But you shouldn't care if you have reasonably recent git everywhere:
> symlinks and their absence already handled: .git/config created by
> init-db contains the configuration parameter for filemode, which
> decides whether it is safe to use the symlinks on the underlying
> filesystem.
No, no no nononononono....
core.filemode is whether the executable bit is trustworthy and
does not have anything to do with symlinked heads, although
these two happen to become problematic on VFAT.
Currently we have USE_SYMLINK_HEAD and have failing symlink()
call fall back on regular file symrefs.
But this may not matter as long as nobody would want to force
regular file symrefs on a filesystem that is capable of doing a
symlink. That is the only thing we cannot do right now.
next prev parent reply other threads:[~2005-11-15 2:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 20:45 Getting rid of symlinks in .git? Petr Baudis
2005-11-11 9:15 ` Simon Richter
2005-11-11 12:43 ` Alex Riesen
2005-11-11 13:01 ` Petr Baudis
[not found] ` <437494B2.30309@hogyros.de>
2005-11-11 18:42 ` Alex Riesen
2005-11-15 2:22 ` Junio C Hamano [this message]
2005-11-15 7:13 ` Alex Riesen
2005-11-11 14:14 ` Johannes Schindelin
2005-11-11 15:05 ` Petr Baudis
2005-11-11 15:40 ` Johannes Schindelin
2005-11-11 15:49 ` Petr Baudis
2005-11-11 16:03 ` Johannes Schindelin
2005-11-11 15:55 ` Nick Hengeveld
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=7vhdaevedu.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=raa.lkml@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).