From: Ben Knoble <ben.knoble@gmail.com>
To: Wesley <wesleys@opperschaap.net>
Cc: Johannes Sixt <j6t@kdbg.org>,
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: Sun, 29 Mar 2026 10:33:58 -0400 [thread overview]
Message-ID: <ACA4834A-2F3F-4817-B2BF-1EF8134FA02A@gmail.com> (raw)
In-Reply-To: <3d8c9b3f-66d0-460d-bd61-a879a6bbfc56@opperschaap.net>
> Le 28 mars 2026 à 11:02, Wesley <wesleys@opperschaap.net> a écrit :
>
> On 3/28/26 03:46, Johannes Sixt wrote:
>
>>> 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.
>
> The ways to do it all involve configuring ssh to configure git, instead of configuring git to configure git. The remote is already configured in git, having your sshIndentityFile and possible other options close to that configuration is beneficial to users. The escape-hatch of core.sshCommand doesn't need to be utilized for a simple "Use this indentityFile on this remote".
Hm. But if you’re connecting to a host (Git or otherwise) via SSH, isn’t the natural place to configure that the SSH client?
I use custom host config to control identify files so that each host I connect to gets a unique identity; some are Git hosts, some are other things.
I don’t yet deal with different connections to the same host, so the only Git configuration I make is to rewrite some HTTPS remote URLs to SSH connection strings.
> The only way to configure git without touching ssh
I think I, at least, claim that this is Git working with SSH, so it is natural that both sides may require tuning.
> There is no need to configure both ssh and possible git with rewrite rules with this patch. Which to me is a cleaner solution. One knob in git for git.
Hence let each do what they do best :) each knob where it belongs.
Just my 2¢. Cheers!
next prev parent reply other threads:[~2026-03-29 14:34 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
2026-03-28 14:59 ` Wesley
2026-03-29 14:33 ` Ben Knoble [this message]
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=ACA4834A-2F3F-4817-B2BF-1EF8134FA02A@gmail.com \
--to=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=wesleys@opperschaap.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.