From: Ricardo Wurmus <rekado@elephly.net>
To: Mark Meyer <mark@ofosos.org>
Cc: 29738@debbugs.gnu.org
Subject: [bug#29738] Add support for HTTP/2 to curl
Date: Sun, 17 Dec 2017 07:31:52 +0100 [thread overview]
Message-ID: <878te1oofb.fsf@elephly.net> (raw)
In-Reply-To: <1513447932.2411366.1207257248.22729BA6@webmail.messagingengine.com>
Hi Mark,
> this patch adds HTTP/2 support to curl, this is a prerequisite to
> closing bug#29733. I am aware that this will trigger about 2500 rebuilt
> packages, but having HTTP/2 in curl seems to be worth the hassle.
We would make this change on the core-updates branch to avoid disrupting
the availability of substitutes, so rebuilding a large number of
packages is not a big problem. Does this patch apply on top of
core-updates?
About the patch: it would be better to separate the two changes. One
commit would add the nghttp2 package, the other would modify the curl
package. Could you please split the patch?
Since curl is used by a great number of packages we need to pay
attention to the size of the closure. How does adding nghttp2 to curl
affect the size of the closure of the curl package? (You can check with
“guix size”.)
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-12-17 6:33 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 ` Ricardo Wurmus [this message]
2017-12-17 8:35 ` [bug#29738] Add support for HTTP/2 to curl 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
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878te1oofb.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=29738@debbugs.gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).