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

Re: Update symlinks after changing core.symlinks

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Apr 2, 2025, 22:41 UTC
Message-ID
<Z-29LsgDvcS0qY5a@tapette.crustytoothpaste.net>
In-Reply-To
<CAArAzAoU9qDj+yLi3pA6wFYdTAk0UvQk4omSWM1RL4D9w5fw_w@mail.gmail.com>
On 2025-04-02 at 07:18:45, Andrej Zhilenkov wrote:
Show 13 quoted lines
> Hello! Is there a direct way to update symlinks in repo after changing
> core.symlinks?
> E.g. update plain files, if it was false, with symlinks or vice versa.
> 
> I've tried `checkout` and `reset` but they have no effect in this case
> (see the snippet below). The only two things that are working:
> - checking out a commit before the symlink was introduced and then
> checking out any commit after (need to know that special commit to
> make it work for those specific symlinks, not practical)
> - removing symlinked files and checking them out specifically (need to
> either have a list or somehow search for those files to reset)
> 
> Is this the way to do it or is there an alternative?

We don't have a way to do this because `core.symlinks` is intended as a hint from Git to itself about whether the file system and operating system support symlinks that's determined when the repository is created. It's not intended that users modify it, much like `core.filemode` or `core.ignorecase`.

What is your particular use case that requires changing this value?
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA
Previous: Andrej ZhilenkovNext: brian m. carlson
Message 2 of 6 in “Update symlinks after changing core.symlinks”
  1. Andrej ZhilenkovApr 2, 2025
  2. brian m. carlsonApr 2, 2025
  3. brian m. carlsonApr 3, 2025
  4. Andrej ZhilenkovApr 4, 2025
  5. brian m. carlsonApr 4, 2025
  6. Andrej ZhilenkovApr 10, 2025

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.