git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Getting rid of symlinks in .git?

From
Junio C Hamano <junkio@cox.net>
Date
Nov 15, 2005, 02:22 UTC
Message-ID
<7vhdaevedu.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<81b0412b0511110443x48415032k8ca40d999071e8a9@mail.gmail.com>
Alex Riesen <raa.lkml@gmail.com> writes:
Show 5 quoted lines
> 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.

Previous: Petr BaudisNext: Alex Riesen
Message 5 of 13 in “Getting rid of symlinks in .git?”
  1. Petr BaudisNov 10, 2005
  2. Simon RichterNov 11, 2005
  3. Alex RiesenNov 11, 2005
  4. Petr BaudisNov 11, 2005
  5. Junio C HamanoNov 15, 2005
  6. Alex RiesenNov 15, 2005
  7. Johannes SchindelinNov 11, 2005
  8. Petr BaudisNov 11, 2005
  9. Johannes SchindelinNov 11, 2005
  10. Petr BaudisNov 11, 2005
  11. Johannes SchindelinNov 11, 2005
  12. Nick HengeveldNov 11, 2005
  13. Alex RiesenNov 11, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.