From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nanako Shiraishi <nanako3@lavabit.com>,
Joey Korkames <joey+floss@kidfixit.com>,
git@vger.kernel.org
Subject: Re: Feature suggestion: support arguments for GIT_PROXY_COMMAND & core.gitproxy
Date: Wed, 30 Dec 2009 06:05:57 -0500 [thread overview]
Message-ID: <20091230110557.GG22959@coredump.intra.peff.net> (raw)
In-Reply-To: <7vmy1051ik.fsf@alter.siamese.dyndns.org>
On Wed, Dec 30, 2009 at 12:06:43AM -0800, Junio C Hamano wrote:
> Nanako Shiraishi <nanako3@lavabit.com> writes:
>
> > Junio, could you tell us what happened to this thread?
> >
> > I think this is probably related to the "textconv" change.
>
> Yeah, you guessed right. I think the unified way to launch user specified
> programs would come first and then spawning proxy the same way as others
> would become trivial.
As a "7/6" on top of my other series, this should just be:
diff --git a/connect.c b/connect.c
index db965c9..838146c 100644
--- a/connect.c
+++ b/connect.c
@@ -432,6 +432,7 @@ static void git_proxy_connect(int fd[2], char *host)
argv[2] = port;
argv[3] = NULL;
memset(&proxy, 0, sizeof(proxy));
+ proxy.use_shell = 1;
proxy.argv = argv;
proxy.in = -1;
proxy.out = -1;
But I will leave it to somebody who actually uses the proxy feature to
test and submit a patch.
-Peff
prev parent reply other threads:[~2009-12-30 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 23:39 Feature suggestion: support arguments for GIT_PROXY_COMMAND & core.gitproxy Joey Korkames
2009-12-19 0:58 ` Joey Korkames
2009-12-30 3:13 ` Nanako Shiraishi
2009-12-30 8:06 ` Junio C Hamano
2009-12-30 11:05 ` Jeff King [this message]
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=20091230110557.GG22959@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joey+floss@kidfixit.com \
--cc=nanako3@lavabit.com \
/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