From: "Christian Kujau via RT" <kernel-helpdesk@rt.linuxfoundation.org>
To: rdunlap@infradead.org
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)
Date: Wed, 24 May 2017 14:42:55 -0400 [thread overview]
Message-ID: <rt-4.4.0-12250-1495651375-1155.40777-6-0@linuxfoundation> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1705241129310.17946@trent.utfs.org>
On Mon, 15 May 2017, Konstantin Ryabitsev via RT wrote:
> On 2017-05-15 14:34:56, francoisvalenduc@gmail.com wrote:
> > It doesn't work with Firefox-53.0. After quite a long time while
> > firefox
> > uses 100% of CPU, I finally get a text file and not a gzip file of the
> > patch for 4.12-rc1. It was almost instantaneous previously. I don't
> > see
> > this as a progress.
>
> Firefox will request a gzip version of the patch, download it and then ungzip
> it for you and display it in the browser. If you'd rather not display
> that, please use a commandline tool like wget or curl to get the patch.
Yeah, same here: clicking on 4.12-rc2/patch on the kernel.org main
page makes Firefox 53 freeze for a few minutes, and then display (!) the
text file (85 MB!) in full. Wow.
> We are trying to identify who are the people who still need to download
> patches as opposed to using git directly, and what their use-case
I never use the links on the kernel.org main page to download patches, but
still: can those be changed to say ".gz" or something, so that $browser
won't _display_ it by default but _download_ it instead?
Thanks,
Christian.
--
BOFH excuse #435:
Internet shut down due to maintenance
next prev parent reply other threads:[~2017-05-24 18:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-40777@linuxfoundation>
2017-05-13 20:57 ` Linux 4.12-rc1 Linus Torvalds
2017-05-14 17:59 ` Linux 4.12-rc1 (file locations) Randy Dunlap
2017-05-15 15:42 ` Linus Torvalds
2017-05-15 15:42 ` [Kernel.org Helpdesk #40777] [linuxfoundation.org #40777] " Linus Torvalds via RT
2017-05-15 18:34 ` François Valenduc
2017-05-15 18:34 ` François Valenduc via RT
[not found] ` <rt-4.4.0-31767-1494873296-832.40777-6-0@linuxfoundation>
2017-05-15 18:42 ` [Kernel.org Helpdesk " Konstantin Ryabitsev via RT
2017-05-24 18:34 ` Christian Kujau
2017-05-24 18:42 ` Christian Kujau via RT [this message]
[not found] ` <rt-4.4.0-12250-1495651374-7.40777-6-0@linuxfoundation>
2017-05-24 20:14 ` Konstantin Ryabitsev via RT
[not found] ` <rt-4.4.0-31807-1494862968-1551.40777-6-0@linuxfoundation>
2017-05-16 21:22 ` Konstantin Ryabitsev via RT
2017-05-15 18:45 ` Konstantin Ryabitsev via RT
2017-05-15 13:15 ` linux-next: stats (Was: Linux 4.12-rc1) Stephen Rothwell
2017-05-15 14:51 ` Sebastian Reichel
2017-05-15 21:32 ` Stephen Rothwell
2017-05-20 16:33 ` Sebastian Reichel
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=rt-4.4.0-12250-1495651375-1155.40777-6-0@linuxfoundation \
--to=kernel-helpdesk@rt.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®