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

submodule path with symlinks

From
KMKyle Marek <psppsn96@gmail.com>
Date
Jul 22, 2026, 18:20 UTC
Message-ID
<cb2bf72a-9bd0-48a7-9e51-2d67f0a9cac4@gmail.com>
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
Message 1 of 1 in “submodule path with symlinks”
  1. Kyle MarekJul 22, 2026

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.