From: Erik Faye-Lund <kusmabite@googlemail.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: [PATCH v3 3/8] imap-send: use run-command API for tunneling
Date: Fri, 16 Oct 2009 16:27:33 +0200 [thread overview]
Message-ID: <40aa078e0910160727g2ebc1e6qe0c3a00186e38569@mail.gmail.com> (raw)
In-Reply-To: <200910142158.59073.j6t@kdbg.org>
Sorry about the late reply, lots of things to do.
On Wed, Oct 14, 2009 at 9:58 PM, Johannes Sixt <j6t@kdbg.org> wrote:
> On Dienstag, 13. Oktober 2009, Erik Faye-Lund wrote:
>> I'm really unsure if it's worth the hassle.
>
> We already depend on the existence of a Bourne shell for our scripted
> commands. There are already more places in the code that run "sh"
> than "/bin/sh".
OK, you've got me convinced. I'll update the patch with this tweak.
--
Erik "kusma" Faye-Lund
prev parent reply other threads:[~2009-10-16 14:27 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 ` [PATCH v3 3/8] imap-send: use run-command API for tunneling Johannes Sixt
2009-10-13 20:27 ` Erik Faye-Lund
2009-10-14 19:58 ` Johannes Sixt
2009-10-16 14:27 ` Erik Faye-Lund [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=40aa078e0910160727g2ebc1e6qe0c3a00186e38569@mail.gmail.com \
--to=kusmabite@googlemail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=kusmabite@gmail.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).