git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrej Zhilenkov <azhilenkov@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
	Andrej Zhilenkov <azhilenkov@gmail.com>,
	 git@vger.kernel.org
Subject: Re: Update symlinks after changing core.symlinks
Date: Fri, 11 Apr 2025 00:29:46 +0500	[thread overview]
Message-ID: <CAArAzArGWE8S2gjvueS+fQ9c56mbzrRV5=0V8SaSX1NUMSXDSg@mail.gmail.com> (raw)
In-Reply-To: <Z--Kz4jsRzm4VSZd@tapette.crustytoothpaste.net>

> 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.

      reply	other threads:[~2025-04-10 19:29 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
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 [this message]

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='CAArAzArGWE8S2gjvueS+fQ9c56mbzrRV5=0V8SaSX1NUMSXDSg@mail.gmail.com' \
    --to=azhilenkov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    /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).