From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1759533AbdEOPts (ORCPT <rfc822;w@1wt.eu>);
        Mon, 15 May 2017 11:49:48 -0400
Received: from smtp2.linuxfoundation.org ([140.211.169.14]:46752 "EHLO
        smtp2.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752157AbdEOPtp (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 15 May 2017 11:49:45 -0400
X-Greylist: delayed 411 seconds by postgrey-1.27 at vger.kernel.org; Mon, 15 May 2017 11:49:45 EDT
Subject: [Kernel.org Helpdesk #40777] [linuxfoundation.org #40777] Re: Linux 4.12-rc1 (file locations)
From: "Linus Torvalds via RT" <kernel-helpdesk@rt.linuxfoundation.org>
Reply-To: kernel-helpdesk@rt.linuxfoundation.org
In-Reply-To: <CA+55aFwv7u5FkELEJiuM7ATAr6KFpUW91UP8HPjh3tuvtQeBzQ@mail.gmail.com>
References: <RT-Ticket-40777@linuxfoundation>
 <CA+55aFx6QnOeQ==-8N0photemZE6uR-G=tGG_mZLYprjCa_eZA@mail.gmail.com>
 <7d545d53-9d9d-02f7-f76d-04033669ef64@infradead.org>
 <CA+55aFwv7u5FkELEJiuM7ATAr6KFpUW91UP8HPjh3tuvtQeBzQ@mail.gmail.com>
Message-ID: <rt-4.4.0-31807-1494862968-1000.40777-6-0@linuxfoundation>
X-RT-Loop-Prevention: linuxfoundation.org
X-RT-Ticket: linuxfoundation.org #40777
X-Managed-BY: RT 4.4.0 (http://www.bestpractical.com/rt/)
X-RT-Originator: torvalds@linux-foundation.org
To: rdunlap@infradead.org
CC: linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Date: Mon, 15 May 2017 11:42:49 -0400
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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