{"thread":{"id":"9347","subject":"core.gitproxy and non-git protocols","startedAt":"2007-08-02T05:21:53Z","lastAt":"2007-08-04T05:43:29Z","messageCount":5,"participants":["David Symonds","Shawn O. Pearce","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"49385","messageId":"ee77f5c20708012221j4d75ff0dl8fbf16cdaf1401bd@mail.gmail.com","threadId":"9347","inReplyTo":null,"subject":"core.gitproxy and non-git protocols","fromName":"David Symonds","fromEmail":"dsymonds@gmail.com","sentAt":"2007-08-02T05:21:53Z","receivedAt":"2007-08-02T05:21:53Z","isPatch":false,"sender":{"key":"dsymonds@gmail.com","avatar":"https://gravatar.com/avatar/b22f5051cbfc11836e36cf7a690e6cde4e225d835e13295ff98d15c7a9ee3c0f?d=mp&s=160"},"body":"Hi,\n\nThe part of the git-config documentation that covers core. gitproxy is\nincorrect: you can't use the core.gitproxy setting to use a proxy\ncommand for ssh://, nor to create your own faux-protocols. In the\ngit_connect function (connect.c), it only references git_proxy_connect\n(and thus the core.gitproxy setting) if (protocol == PROTO_GIT).\n\nI have a situation where I'd like to push to a remote git repository\non a machine that is a little weird to access, so I need two different\ntypes of ssh'ing to reach it depending on my location. That is easily\nscriptable, which is how I did it with SVN (ended up with a\nsvn+voltron:// protocol), but is not currently possible with git.\n\nIt'd be great if (a) the documentation could be fixed, or (b) the\nproxy-picking code could be at least extended to ssh:// protocols, and\npreferrably extended to defining custom protocols.\n\nThanks,\n\nDave.\n"},{"id":"49387","messageId":"20070802053151.GH20052@spearce.org","threadId":"9347","inReplyTo":"ee77f5c20708012221j4d75ff0dl8fbf16cdaf1401bd@mail.gmail.com","subject":"Re: core.gitproxy and non-git protocols","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-08-02T05:31:51Z","receivedAt":"2007-08-02T05:31:51Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"David Symonds <dsymonds@gmail.com> wrote:\n> It'd be great if (a) the documentation could be fixed, or (b) the\n> proxy-picking code could be at least extended to ssh:// protocols, and\n> preferrably extended to defining custom protocols.\n\nDid you try setting GIT_SSH envvar to point to a script that does\nwhat you need?  I do this in one particular case...\n\n-- \nShawn.\n"},{"id":"49651","messageId":"f90hhb$3tg$1@sea.gmane.org","threadId":"9347","inReplyTo":"ee77f5c20708012221j4d75ff0dl8fbf16cdaf1401bd@mail.gmail.com","subject":"Re: core.gitproxy and non-git protocols","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-08-04T00:33:52Z","receivedAt":"2007-08-04T00:33:52Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"[Cc: David Symonds <dsymonds@gmail.com>, gmane.comp.version-control.git]\n\nDavid Symonds wrote:\n\n> I have a situation where I'd like to push to a remote git repository\n> on a machine that is a little weird to access, so I need two different\n> types of ssh'ing to reach it depending on my location. That is easily\n> scriptable, which is how I did it with SVN (ended up with a\n> svn+voltron:// protocol), but is not currently possible with git.\n\nSee http://git.or.cz/gitwiki/GitTip, section \"How to push/pull via ssh to\nhost behind gateway?\". It describes two solutions: first, using\nProxyCommand option of ssh and netcat utility on gateway, second via ssh\ntunnel set up.\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"},{"id":"49652","messageId":"f90his$3tg$2@sea.gmane.org","threadId":"9347","inReplyTo":"20070802053151.GH20052@spearce.org","subject":"Re: core.gitproxy and non-git protocols","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-08-04T00:34:41Z","receivedAt":"2007-08-04T00:34:41Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Shawn O. Pearce wrote:\n\n> David Symonds <dsymonds@gmail.com> wrote:\n\n>> It'd be great if (a) the documentation could be fixed, or (b) the\n>> proxy-picking code could be at least extended to ssh:// protocols, and\n>> preferrably extended to defining custom protocols.\n> \n> Did you try setting GIT_SSH envvar to point to a script that does\n> what you need?  I do this in one particular case...\n\nGIT_SSH environmental variable is *not described* anywhere in the\ndocumentation. Would you be so kind?\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"},{"id":"49666","messageId":"20070804054329.GO20052@spearce.org","threadId":"9347","inReplyTo":"f90his$3tg$2@sea.gmane.org","subject":"Re: core.gitproxy and non-git protocols","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-08-04T05:43:29Z","receivedAt":"2007-08-04T05:43:29Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Jakub Narebski <jnareb@gmail.com> wrote:\n> Shawn O. Pearce wrote:\n> > \n> > Did you try setting GIT_SSH envvar to point to a script that does\n> > what you need?  I do this in one particular case...\n> \n> GIT_SSH environmental variable is *not described* anywhere in the\n> documentation. Would you be so kind?\n\nWhow.  It really isn't documented.\n\nOK, I'll send a documentation patch in a few minutes.\n\n-- \nShawn.\n"}]}