From: "brian m. carlson" <sandals@crustytoothpaste•net>
To: Andrej Zhilenkov <azhilenkov@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: Update symlinks after changing core.symlinks
Date: Wed, 2 Apr 2025 22:41:50 +0000 [thread overview]
Message-ID: <Z-29LsgDvcS0qY5a@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CAArAzAoU9qDj+yLi3pA6wFYdTAk0UvQk4omSWM1RL4D9w5fw_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
On 2025-04-02 at 07:18:45, Andrej Zhilenkov wrote:
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2025-04-02 22:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 7:18 Update symlinks after changing core.symlinks Andrej Zhilenkov
2025-04-02 22:41 ` brian m. carlson [this message]
2025-04-03 22:25 ` brian m. carlson
2025-04-04 5:51 ` Andrej Zhilenkov
2025-04-04 7:31 ` brian m. carlson
2025-04-10 19:29 ` Andrej Zhilenkov
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=Z-29LsgDvcS0qY5a@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste$(echo .)net \
--cc=azhilenkov@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/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