From: Nicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Stefan Beller <sbeller@google.com>
Cc: Johannes Sixt <j6t@kdbg.org>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [RFC 0/3] imap-send curl tunnelling support
Date: Mon, 21 Aug 2017 09:27:03 +0200 [thread overview]
Message-ID: <4a5f9d64-0709-b6b0-c398-6887f1f7f4c0@morey-chaisemartin.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1708161429510.19382@virtualbox>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
(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.
Nicolas
Le 16/08/2017 à 14:30, Johannes Schindelin a écrit :
> Hi,
>
> On Tue, 15 Aug 2017, Stefan Beller wrote:
>
>> On Tue, Aug 15, 2017 at 10:49 AM, Nicolas Morey-Chaisemartin
>> <nicolas@morey-chaisemartin.com> wrote:
>>> Ping.
>>>
>>> I'd like to get feedback from Windows developer on patch #2
>>> Patch#3 will probably need some updates as I expected Jeff old curl drop patches to make it in.
>>> As it seems to be going another way a few more ifdefs will be required
>> +cc Windows devs
> I can has easy-to-pull branch, please?
>
> Thanks,
> Dscho
[-- Attachment #2: 0x801BDDB825988F64.asc --]
[-- Type: application/pgp-keys, Size: 3774 bytes --]
next prev parent reply other threads:[~2017-08-21 7:33 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 [this message]
2017-08-22 17:10 ` Johannes Sixt
2017-08-22 18:22 ` Nicolas Morey-Chaisemartin
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=4a5f9d64-0709-b6b0-c398-6887f1f7f4c0@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).