From: Johannes Sixt <j6t@kdbg.org>
To: msysgit@googlegroups.com
Cc: "Erik Faye-Lund" <kusmabite@googlemail.com>,
git@vger.kernel.org, "Erik Faye-Lund" <kusmabite@gmail.com>
Subject: Re: [PATCH v3 3/8] imap-send: use run-command API for tunneling
Date: Tue, 13 Oct 2009 21:59:11 +0200 [thread overview]
Message-ID: <200910132159.11616.j6t@kdbg.org> (raw)
In-Reply-To: <1255461925-2244-4-git-send-email-kusmabite@gmail.com>
On Dienstag, 13. Oktober 2009, Erik Faye-Lund wrote:
> + argv[0] = "/bin/sh";
> + argv[1] = "-c";
> + argv[2] = srvc->tunnel;
> + argv[3] = NULL;
Is there a particular reason that you run "/bin/sh" with a path? I doubt that
this works on Windows.
-- Hannes
next prev parent reply other threads:[~2009-10-13 19:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 19:25 [PATCH v3 0/8] imap-send: Windows support Erik Faye-Lund
2009-10-13 19:25 ` [PATCH v3 1/8] imap-send: remove useless uid code Erik Faye-Lund
2009-10-13 19:25 ` [PATCH v3 2/8] imap-send: use separate read and write fds Erik Faye-Lund
2009-10-13 19:25 ` [PATCH v3 3/8] imap-send: use run-command API for tunneling Erik Faye-Lund
2009-10-13 19:25 ` [PATCH v3 4/8] imap-send: fix compilation-error on Windows Erik Faye-Lund
2009-10-13 19:25 ` [PATCH v3 5/8] imap-send: build imap-send " Erik Faye-Lund
2009-10-13 19:25 ` [PATCH v3 6/8] mingw: wrap SSL_set_(w|r)fd to call _get_osfhandle Erik Faye-Lund
2009-10-13 19:25 ` [PATCH v3 7/8] mingw: enable OpenSSL Erik Faye-Lund
2009-10-13 19:25 ` [PATCH v3 8/8] MSVC: Enable OpenSSL, and translate -lcrypto Erik Faye-Lund
2009-10-13 19:57 ` [PATCH v3 5/8] imap-send: build imap-send on Windows Johannes Sixt
2009-10-13 20:16 ` Erik Faye-Lund
2009-10-13 21:34 ` Erik Faye-Lund
2009-10-13 19:59 ` Johannes Sixt [this message]
2009-10-13 20:27 ` [PATCH v3 3/8] imap-send: use run-command API for tunneling Erik Faye-Lund
2009-10-14 19:58 ` Johannes Sixt
2009-10-16 14:27 ` Erik Faye-Lund
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=200910132159.11616.j6t@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=kusmabite@googlemail.com \
--cc=msysgit@googlegroups.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;
as well as URLs for NNTP newsgroup(s).