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

Re: How should submodules use different sshCommand during initial update?

From
SXShibo Xia <sbxia25@gmail.com>
Date
Apr 14, 2026, 07:25 UTC
Message-ID
<CAAC4ekoduJ03xjA08GouE_r9sJHnS4aTD3GgaA3GChdn6t_v8w@mail.gmail.com>
In-Reply-To
<20260414061558.GA2902306@coredump.intra.peff.net>
Thank you, this is very helpful.

The includeIf approach and the two-step workaround do seem workable, but they still feel awkward when different submodules need different settings during the initial clone.

I would like to try a small RFC patch for this.

My current direction is a general per-submodule config injection mechanism for submodule update --init, so that config can be passed to the underlying clone/fetch for one submodule without affecting others.

Does that sound like a reasonable direction for a first RFC patch?

Thanks, Shibo Xia

Jeff King <peff@peff.net> 于2026年4月14日周二 14:16写道:
Show 66 quoted lines
>
> On Tue, Apr 14, 2026 at 09:28:20AM +0800, Shibo Xia wrote:
>
> > My concern is that this still solves the problem indirectly through URL
> > rewriting / SSH host aliasing, rather than allowing the submodule's SSH
> > behavior itself to be configured more directly.
> >
> > So I think this answers the practical "how can this be done today?" part,
> > but I am still wondering whether there is a reason Git should not support a
> > more direct per-submodule sshCommand-style configuration.
>
> For arbitrary per-submodule config, I can think of two approaches:
>
> One is conditional includeIf directives in your ~/.gitconfig, matching
> based on the submodule names. Like:
>
>   # replace PARENT and SUBMODULE with your filesystem names
>   [includeIf "gitdir:**/PARENT/.git/modules/SUBMODULE"]
>   path = .gitconfig-submodule
>
> and then in ~/.gitconfig-submodule, you'd have:
>
>   [core]
>   sshCommand = whatever
>
> This works, but it's kind of gross, as it depends on the module naming
> scheme (and isn't there a proposal to make these more opaque? I didn't
> follow it). And of course you're not actually putting the config in the
> submodule, but rather polluting your user-level config with it (which
> might or might not be preferable, depending on what you're trying to
> configure).
>
> The second thought is that we faced the same problem with "git clone"
> itself: you might want to tweak some config after the repo is
> initialized but before we fetch anything. We added the "clone -c" option
> for that. It would seem reasonable to me to have a similar option that
> is passed along to git-clone under the hood. We already have ways to
> pass through options like --single-branch for the same reason.
>
> And then presumably you could do:
>
>   git submodule update --init -c core.sshCommand=whatever
>
> In the meantime, as a workaround I suspect you could do it in two steps,
> like:
>
>   # set it for the initial clone; this is using the one-shot "git -c",
>   # not "clone -c" that will actually save the result in the
>   # new repo
>   git -c core.sshCommand=whatever submodule update --init
>
>   # and then save it for subsequent fetches
>   git submodule foreach 'git config core.sshCommand whatever'
>
> It's rather unwieldy. And I think gets weird if you want to cover only a
> subset of paths, as it doesn't look like "submodule foreach" allows
> that. So you might be stuck with:
>
>   git -c core.sshCommand=whatever submodule update --init some-path
>   git -C .git/modules/some-path config core.sshCommand whatever
>
> which is back to being overly intimate with the filesystem layout. There
> might be a better way to do a per-module command. I don't really use
> submodules myself.
>
> -Peff
Previous: Jeff King
Message 5 of 5 in “How should submodules use different sshCommand during initial update?”
  1. Shibo XiaApr 13, 2026
  2. Junio C HamanoApr 13, 2026
  3. Shibo XiaApr 14, 2026
  4. Jeff KingApr 14, 2026
  5. Shibo XiaApr 14, 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.