From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933709AbdEOPmn (ORCPT ); Mon, 15 May 2017 11:42:43 -0400 Received: from mail-io0-f172.google.com ([209.85.223.172]:35668 "EHLO mail-io0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933174AbdEOPml (ORCPT ); Mon, 15 May 2017 11:42:41 -0400 MIME-Version: 1.0 In-Reply-To: <7d545d53-9d9d-02f7-f76d-04033669ef64@infradead.org> References: <7d545d53-9d9d-02f7-f76d-04033669ef64@infradead.org> From: Linus Torvalds Date: Mon, 15 May 2017 08:42:40 -0700 X-Google-Sender-Auth: -jTZO3CkND35iY5DA5FyeTMvM50 Message-ID: Subject: Re: Linux 4.12-rc1 (file locations) To: Randy Dunlap , Konstantin Ryabitsev Cc: Linux Kernel Mailing List , helpdesk@kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, May 14, 2017 at 10:59 AM, Randy Dunlap 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