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

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

From
Ben Knoble <ben.knoble@gmail.com>
Date
Mar 29, 2026, 14:33 UTC
Message-ID
<ACA4834A-2F3F-4817-B2BF-1EF8134FA02A@gmail.com>
In-Reply-To
<3d8c9b3f-66d0-460d-bd61-a879a6bbfc56@opperschaap.net>
Show 17 quoted lines
> 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!
Previous: WesleyNext: brian m. carlson
Message 22 of 24 in “Add support for per-remote and per-namespace SSH options”
  1. 0/3 Add support for per-remote and per-namespace SSH optionsWesley Schwengle, Mar 26, 2026
  2. 1/3 connect: Rename name to command in connect_git()Wesley Schwengle, Mar 26, 2026
  3. Jeff KingMar 27, 2026
  4. WesleyMar 28, 2026
  5. Jeff KingMar 28, 2026
  6. WesleyMar 28, 2026
  7. 2/3 connect: Add transport->remote->name to git_connect()Wesley Schwengle, Mar 26, 2026
  8. Jeff KingMar 27, 2026
  9. 3/3 connect: Add support for per-remote and per-namespace SSH optionsWesley Schwengle, Mar 26, 2026
  10. Jeff KingMar 27, 2026
  11. WesleyMar 28, 2026
  12. Jeff KingMar 28, 2026
  13. WesleyMar 28, 2026
  14. Johannes SixtMar 27, 2026
  15. WesleyMar 27, 2026
  16. Junio C HamanoMar 27, 2026
  17. WesleyMar 27, 2026
  18. brian m. carlsonMar 27, 2026
  19. WesleyMar 28, 2026
  20. Johannes SixtMar 28, 2026
  21. WesleyMar 28, 2026
  22. Ben KnobleMar 29, 2026
  23. brian m. carlsonMar 27, 2026
  24. Junio C HamanoMar 27, 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.