All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linus Torvalds via RT" <kernel-helpdesk@rt.linuxfoundation.org>
To: rdunlap@infradead.org
Cc: linux-kernel@vger.kernel.org
Subject: [Kernel.org Helpdesk #40777] [linuxfoundation.org #40777] Re: Linux 4.12-rc1 (file locations)
Date: Mon, 15 May 2017 11:42:49 -0400	[thread overview]
Message-ID: <rt-4.4.0-31807-1494862968-1000.40777-6-0@linuxfoundation> (raw)
In-Reply-To: <CA+55aFwv7u5FkELEJiuM7ATAr6KFpUW91UP8HPjh3tuvtQeBzQ@mail.gmail.com>

On Sun, May 14, 2017 at 10:59 AM, Randy Dunlap <rdunlap@infradead.org> wrote:
>
> Can the generated files please be put in the same places that (most or
> all) previous releases have used?

I will leave this to Konstantin.. There may well be practical reasons
for the movement.

> Oh, and the patch file (on https://kernel.org) is a text file, not a
> zipped file (as in previous releases).

Well, if you use a browser, the normal browser compression (behind
your back) should be in effect. So you won't actually be wasting the
bandwidth.

If you use wget, you have to manually ask for it. Quoting Konstantin
from an earlier discussion:

> Yes, this is implemented on the http protocol level -- but you have to
> tell wget to request it:
>
> wget -O test.patch.gz \
>  --header="accept-encoding: gzip" \
>  https://git.kernel.org/...
>
> Browsers do the requesting and ungzipping automatically, but not cmdline
> tools.

so the capability is there, it's just not done as several individual
files any more.

                 Linus

  reply	other threads:[~2017-05-15 15:49 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       ` Linus Torvalds via RT [this message]
2017-05-15 18:34         ` [Kernel.org Helpdesk #40777] [linuxfoundation.org #40777] " 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
     [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-31807-1494862968-1000.40777-6-0@linuxfoundation \
    --to=kernel-helpdesk@rt.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 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.