All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev via RT"  <kernel-helpdesk@rt.linuxfoundation.org>
To: rdunlap@infradead.org
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: [Kernel.org Helpdesk #40777] Re: Linux 4.12-rc1 (file locations)
Date: Mon, 15 May 2017 14:45:28 -0400	[thread overview]
Message-ID: <rt-4.4.0-31806-1494873928-478.40777-6-0@linuxfoundation> (raw)
In-Reply-To: <7d545d53-9d9d-02f7-f76d-04033669ef64@infradead.org>

On 2017-05-14 13:59:22, rdunlap@infradead.org wrote:
> 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.

This is intentional to indicate the transient autogenerated nature of these files. They don't exist in the /pub tree and therefore it is misleading to rewrite URLs to place them there.

> Can the generated files please be put in the same places that (most or
> all) previous releases have used?

Not unless there is a convincing reason to do so (and please feel free to provide it, as this is not a final change and can always be undone should the counter-arguments be convincing).

Regards,
-- 
Konstantin Ryabitsev
Senior Systems Administrator
Linux Foundation Collab Projects
Montréal, Québec

  parent reply	other threads:[~2017-05-15 18:45 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
     [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 [this message]
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-31806-1494873928-478.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 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.