From: mricon at kernel.org (Konstantin Ryabitsev)
Subject: RFE: have a way to request compressed patches and rawdiffs
Date: Fri, 28 Apr 2017 16:46:34 +0000 [thread overview]
Message-ID: <CAMwyc-RDJnbfroPCVZ+na2Obhe+6ELA6sHC_6854C8sY53_8iA@mail.gmail.com> (raw)
Since I'm on an RFE binge, here's another one. :)
Some of the rawdiffs we have been generating end up pretty large (e.g.
linux-next to mainline rawdiff is around 80MB). We compress them using http
protocol compression, but the reality is that most people would be getting
these using wget or curl, which do not add the "accept-encoding: gzip"
header and therefore get the uncompressed version.
It would be great to be able to tell cgit to generate and send compressed
versions of raw output like patches or rawdiffs.
Thanks for all your help.
Best,
Konstantin
--
Konstantin Ryabitsev
Director, IT Infrastructure Security
The Linux Foundation
+1-971-258-2363
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20170428/c71dc209/attachment.html>
next reply other threads:[~2017-04-28 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 16:46 mricon [this message]
2017-05-01 11:00 ` john
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=CAMwyc-RDJnbfroPCVZ+na2Obhe+6ELA6sHC_6854C8sY53_8iA@mail.gmail.com \
--to=cgit@lists.zx2c4.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).