Re: Update symlinks after changing core.symlinks

From: Andrej Zhilenkov <azhilenkov@gmail.com>
Date: Apr 10, 2025, 19:29 UTC
Message-ID: <CAArAzArGWE8S2gjvueS+fQ9c56mbzrRV5=0V8SaSX1NUMSXDSg@mail.gmail.com>
In-Reply-To: <Z--Kz4jsRzm4VSZd@tapette.crustytoothpaste.net>

Show 7 quoted lines

> Ah, there I disagree.  I think if you have privileges to create
> symlinks, you probably want them to always be enabled, and if not, you
> don't really have a choice and they'll be disabled.  My experience with
> using repositories with symbolic links is that typically they don't
> function at all (or, if the maintainer has taken great care, only with
> greatly reduced functionality) if the symlinks are missing.  I think
> Git's repository is by far the exception here.

I personally agree that everyone should just enable them globally if they can. Still, maybe it's just me, but I don't like proposing global changes to users when they need it just for some repo.

And also, I keep seeing Windows users having `git config --local core.symlinks` set to `false` (God knows why - in theory Git for Windows suppose to set `--system core.symlinks` to `false`, `--local` shouldn't be affected by this) and just setting `--local` helps covering those cases too.