From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759522AbdENR7c (ORCPT ); Sun, 14 May 2017 13:59:32 -0400 Received: from merlin.infradead.org ([205.233.59.134]:39656 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758982AbdENR72 (ORCPT ); Sun, 14 May 2017 13:59:28 -0400 Subject: Re: Linux 4.12-rc1 (file locations) To: Linus Torvalds , Linux Kernel Mailing List , helpdesk@kernel.org References: From: Randy Dunlap Message-ID: <7d545d53-9d9d-02f7-f76d-04033669ef64@infradead.org> Date: Sun, 14 May 2017 10:59:15 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/13/17 13:57, Linus Torvalds wrote: > One thing worth noting - I haven't uploaded diffs or tar-balls for > this rc. Those should now be automagically generated by kernel.org for > the rc's, but that also means that they won't be signed by my key. If > you really care about signing, get the git repo and check the tag. There was some delay (don't know how much), but a bigger problem is the file(s) locations and (new) directory structure for them. Can the generated files please be put in the same places that (most or all) previous releases have used? Oh, and the patch file (on https://kernel.org) is a text file, not a zipped file (as in previous releases). thanks. -- ~Randy