From: "David Symonds" <dsymonds@gmail.com>
To: git@vger.kernel.org
Subject: core.gitproxy and non-git protocols
Date: Thu, 2 Aug 2007 15:21:53 +1000 [thread overview]
Message-ID: <ee77f5c20708012221j4d75ff0dl8fbf16cdaf1401bd@mail.gmail.com> (raw)
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 reply other threads:[~2007-08-02 5:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 5:21 David Symonds [this message]
2007-08-02 5:31 ` core.gitproxy and non-git protocols Shawn O. Pearce
2007-08-04 0:34 ` Jakub Narebski
2007-08-04 5:43 ` Shawn O. Pearce
2007-08-04 0:33 ` Jakub Narebski
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=ee77f5c20708012221j4d75ff0dl8fbf16cdaf1401bd@mail.gmail.com \
--to=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).