Git development
 help / color / mirror / Atom feed
From: Kyle Marek <psppsn96@gmail.com>
To: git@vger.kernel.org
Subject: submodule path with symlinks
Date: Wed, 22 Jul 2026 14:20:34 -0400	[thread overview]
Message-ID: <cb2bf72a-9bd0-48a7-9e51-2d67f0a9cac4@gmail.com> (raw)

Hello,

I've just hit this change in behavior introduced ~2 years ago, where 
submodule paths are no longer allowed to contain symlinks [1].

This change has broken a practice that I have used repeatedly over the 
years, where several worktrees share the same copy of their submodules. 
It has been very useful for project organization, but no longer works on 
updated systems for "security" reasons. Please, I understand the risks 
associated with symlinks, I do not want to be "protected from myself", 
and I do not want to re-architect affected projects.

I see there is even a TODO comment about exactly this issue [2]:

 > TODO: allow exempting it via `safe.submodule.path` or something

I'm surprised to see that this change went through without an 
accompanying commit to allowing exceptions or allowing the user accept 
the risks associated with symlinks.

Is there interest in implementing the TODO? Will you accept a patch for 
this?

Thank you,
Kyle Marek

[1]: https://git.kernel.org/pub/scm/git/git.git/commit/?id=e8d0608944486019ea0e1ed2ed29776811a565c2

[2]: https://git.kernel.org/pub/scm/git/git.git/tree/builtin/submodule--helper.c?id=e8d0608944486019ea0e1ed2ed29776811a565c2#n2679


                 reply	other threads:[~2026-07-22 18:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cb2bf72a-9bd0-48a7-9e51-2d67f0a9cac4@gmail.com \
    --to=psppsn96@gmail.com \
    --cc=git@vger.kernel.org \
    /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