From: Tobias Geerinckx-Rice <me@tobias.gr>
To: leo@famulari.name
Cc: 29738@debbugs.gnu.org, mark@ofosos.org
Subject: [bug#29738] Next core-updates cycle
Date: Sat, 6 Jan 2018 22:23:29 +0100 [thread overview]
Message-ID: <6f67b89d-f6bd-c8c0-fa79-dff3b9d64883@tobias.gr> (raw)
In-Reply-To: <20180106185937.GA29853@jasmine.lan>
[-- Attachment #1.1: Type: text/plain, Size: 659 bytes --]
Mark, Leo,
Leo Famulari wrote on 06/01/18 at 19:59:
> On Fri, Jan 05, 2018 at 01:54:02AM +0100, Tobias Geerinckx-Rice wrote:
>> Most importantly, this builds the entire nghttp2 package, not only the
>> core library required by curl. The tools that use it aren't just toys or
>> examples as in some other packages. I use them regularly.
>
> Okay, this sounds like a more complete package.
>
> Can you keep it yourself for the next core-updates cycle? And I'll
> remove Mark's from my branch.
OK. I'll push nghttp2 and the gnurl patch to master in a few days, and
keep HTTP/2 curl in my core-updates-next. Thanks!
Kind regards,
T G-R
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 248 bytes --]
next prev parent reply other threads:[~2018-01-06 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 18:12 [bug#29738] Add support for HTTP/2 to curl Mark Meyer
2017-12-16 18:14 ` [bug#29738] Patch was missing Mark Meyer
2017-12-17 6:31 ` [bug#29738] Add support for HTTP/2 to curl Ricardo Wurmus
2017-12-17 8:35 ` Mark Meyer
2018-01-04 17:29 ` [bug#29738] Next core-updates cycle Mark Meyer
2018-01-04 17:53 ` Leo Famulari
2018-01-05 0:54 ` Tobias Geerinckx-Rice
2018-01-05 1:59 ` Tobias Geerinckx-Rice
2018-01-06 18:59 ` Leo Famulari
2018-01-06 19:03 ` Mark Meyer
2018-01-06 21:23 ` Tobias Geerinckx-Rice [this message]
2018-03-14 17:17 ` bug#29738: Add support for HTTP/2 to curl Tobias Geerinckx-Rice
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=6f67b89d-f6bd-c8c0-fa79-dff3b9d64883@tobias.gr \
--to=me@tobias.gr \
--cc=29738@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=mark@ofosos.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.