Re: [PATCH 0/3] Add support for per-remote and per-namespace SSH options

From: Johannes Sixt <j6t@kdbg.org>
Date: Mar 28, 2026, 07:46 UTC
Message-ID: <becf040c-b425-4fd1-affa-b6368c812b42@kdbg.org>
In-Reply-To: <09c5fe7d-8379-4f68-bf1c-9869e2924cb8@opperschaap.net>

Am 27.03.26 um 17:49 schrieb Wesley:

Show 10 quoted lines

> On 3/27/26 12:10, Junio C Hamano wrote:
>> I somehow thought that this practice is so widespread that it was
>> one of the few first things any new people learn to do, but perhaps
>> we do not have a good documentation coverage?
> 
> As said before it is weird thing to configure a global ssh configuration
> just for git transport. It doesn't make much sense.
> 
> The problem with ssh_config usage is that you need to change your ssh
> config, which is machine global, not just git.

Are thinking about the SSH configuration in /etc/ssh? You do not have to change that. There is also a .ssh/config in the user's home directory. That configuration isn't machine global, it's obviously per user. And the way to make the configuration work only for Git is precisely to use fake host names that are only used in remote URLs of Git repositories.

Show 5 quoted lines

> And not portable across
> teams with configurations committed to git. Myrepos is a good example of
> this. My former employer had this and I know the Perl metacpan project
> also uses mysrepos. Changing every URL dynamically in committed configs
> isn't really a nice ask.

I cannot comment on this, because I do not know these tools.

There are ways to achieve a considerable amount of customization of SSH connections with existing tools. If you need additional features, you should sell your change with a more specific justification, including examples that show reviewers who do not know the tools you are using what is needed, but missing.

-- Hannes