From: Johannes Sixt <j6t@kdbg•org>
To: Wesley <wesleys@opperschaap•net>
Cc: git@vger•kernel.org, Junio C Hamano <gitster@pobox•com>
Subject: Re: [PATCH 0/3] Add support for per-remote and per-namespace SSH options
Date: Sat, 28 Mar 2026 08:46:46 +0100 [thread overview]
Message-ID: <becf040c-b425-4fd1-affa-b6368c812b42@kdbg.org> (raw)
In-Reply-To: <09c5fe7d-8379-4f68-bf1c-9869e2924cb8@opperschaap.net>
Am 27.03.26 um 17:49 schrieb Wesley:
> 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.
> 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
next prev parent reply other threads:[~2026-03-28 7:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 23:37 [PATCH 0/3] Add support for per-remote and per-namespace SSH options Wesley Schwengle
2026-03-26 23:37 ` [PATCH 1/3] connect: Rename name to command in connect_git() Wesley Schwengle
2026-03-27 21:33 ` Jeff King
2026-03-28 0:58 ` Wesley
2026-03-28 1:44 ` Jeff King
2026-03-28 2:01 ` Wesley
2026-03-26 23:37 ` [PATCH 2/3] connect: Add transport->remote->name to git_connect() Wesley Schwengle
2026-03-27 21:39 ` Jeff King
2026-03-26 23:37 ` [PATCH 3/3] connect: Add support for per-remote and per-namespace SSH options Wesley Schwengle
2026-03-27 21:45 ` Jeff King
2026-03-28 0:43 ` Wesley
2026-03-28 2:03 ` Jeff King
2026-03-28 2:25 ` Wesley
2026-03-27 7:51 ` [PATCH 0/3] " Johannes Sixt
2026-03-27 15:04 ` Wesley
2026-03-27 16:10 ` Junio C Hamano
2026-03-27 16:49 ` Wesley
2026-03-27 22:06 ` brian m. carlson
2026-03-28 1:02 ` Wesley
2026-03-28 7:46 ` Johannes Sixt [this message]
2026-03-28 14:59 ` Wesley
2026-03-29 14:33 ` Ben Knoble
2026-03-27 21:51 ` brian m. carlson
2026-03-27 22:25 ` Junio C Hamano
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=becf040c-b425-4fd1-affa-b6368c812b42@kdbg.org \
--to=j6t@kdbg$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=wesleys@opperschaap$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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