From: Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Stefan Beller <sbeller@google.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [RFC 0/3] imap-send curl tunnelling support
Date: Tue, 22 Aug 2017 20:22:52 +0200 [thread overview]
Message-ID: <0851413b-b83a-7290-76d4-249a49eb30c9@morey-chaisemartin.com> (raw)
In-Reply-To: <63e3ebea-ad4e-14d7-1170-594390af8e06@kdbg.org>
This was sadly kind of expected...
I need to look for another way to handle this on Windows.
Thanks for the test
Nicolas
Le 22/08/2017 à 19:10, Johannes Sixt a écrit :
> Am 21.08.2017 um 09:27 schrieb Nicolas Morey-Chaisemartin:
>> (Sent a reply from my phone while out of town but couldn't find it so here it is again)
>>
>> It's available on my github:
>> https://github.com/nmorey/git/tree/dev/curl-tunnel
>>
>> The series had been stlighly changed since the patch were posted, mostly to add the proper ifdefs to handle older curl versions.
>
> This does not build for me on Windows due to a missing socketpair() function. But I am working in an old environment, so I do not know whether this statement has much value.
>
> -- Hannes
next prev parent reply other threads:[~2017-08-22 18:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 14:43 [RFC 0/3] imap-send curl tunnelling support Nicolas Morey-Chaisemartin
2017-08-09 14:46 ` [RFC 1/3] imap-send: move tunnel setup to its own function Nicolas Morey-Chaisemartin
2017-08-09 14:46 ` [RFC 2/3] imap-send: use a socketpair instead of pipe to communicate with the tunnel Nicolas Morey-Chaisemartin
2017-08-09 14:46 ` [RFC 3/3] imap_send: add support for curl over tunnel Nicolas Morey-Chaisemartin
2017-08-15 17:49 ` [RFC 0/3] imap-send curl tunnelling support Nicolas Morey-Chaisemartin
2017-08-15 18:18 ` Stefan Beller
2017-08-16 12:30 ` Johannes Schindelin
2017-08-21 7:27 ` Nicolas Morey-Chaisemartin
2017-08-22 17:10 ` Johannes Sixt
2017-08-22 18:22 ` Nicolas Morey-Chaisemartin [this message]
2017-08-23 22:35 ` Johannes Schindelin
2017-08-16 8:34 ` Jeff King
2017-08-21 7:34 ` Nicolas Morey-Chaisemartin
2017-08-23 21:43 ` Jeff King
2017-08-24 8:00 ` Nicolas Morey-Chaisemartin
2017-08-24 13:53 ` Jeff King
2017-08-24 14:02 ` Daniel Stenberg
2017-08-24 14:30 ` Jeff King
2017-08-24 21:22 ` Daniel Stenberg
2017-08-24 14:15 ` Nicolas Morey-Chaisemartin
2017-08-24 14:28 ` Jeff King
[not found] ` <7ee8331d-e154-7539-e000-4087406f39fa@suse.de>
2017-08-16 8:39 ` Jeff King
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=0851413b-b83a-7290-76d4-249a49eb30c9@morey-chaisemartin.com \
--to=nicolas@morey-chaisemartin.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=sbeller@google.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).