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

core.gitproxy and non-git protocols

From
David Symonds <dsymonds@gmail.com>
Date
Aug 2, 2007, 05:21 UTC
Message-ID
<ee77f5c20708012221j4d75ff0dl8fbf16cdaf1401bd@mail.gmail.com>
Hi,

The part of the git-config documentation that covers core. gitproxy is incorrect: you can't use the core.gitproxy setting to use a proxy command for ssh://, nor to create your own faux-protocols. In the git_connect function (connect.c), it only references git_proxy_connect (and thus the core.gitproxy setting) if (protocol == PROTO_GIT).

I have a situation where I'd like to push to a remote git repository on a machine that is a little weird to access, so I need two different types of ssh'ing to reach it depending on my location. That is easily scriptable, which is how I did it with SVN (ended up with a svn+voltron:// protocol), but is not currently possible with git.

It'd be great if (a) the documentation could be fixed, or (b) the proxy-picking code could be at least extended to ssh:// protocols, and preferrably extended to defining custom protocols.

Thanks,
Dave.
Next: Shawn O. Pearce
Message 1 of 5 in “core.gitproxy and non-git protocols”
  1. David SymondsAug 2, 2007
  2. Shawn O. PearceAug 2, 2007
  3. Jakub NarebskiAug 4, 2007
  4. Shawn O. PearceAug 4, 2007
  5. Jakub NarebskiAug 4, 2007

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.