From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E4392C3A5A2 for ; Sat, 24 Aug 2019 01:18:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B71DC21848 for ; Sat, 24 Aug 2019 01:18:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566609489; bh=6f1HDvkdNDwLdAe/vvH9HQBpuyq4dH6kyBR4+kjmGhA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Q3Jj9/SYj1/jKEFKTO1ugKn5IvjRkXqyct50pU/MFGYL9bMBwOzEu5Bw/YaGHWQ0O V/AsErMZzsx6lk/lrOT0d5D95R/woX9tiTTQzhVlhpSHdWd654BdcMUHOsomoP1Vib XlxmC9tDhaE8I1JRAGrVGduV0LmbU2WCX07DbZe0= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725924AbfHXBSJ (ORCPT ); Fri, 23 Aug 2019 21:18:09 -0400 Received: from mail.kernel.org ([198.145.29.99]:34046 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725782AbfHXBSJ (ORCPT ); Fri, 23 Aug 2019 21:18:09 -0400 Received: from localhost (unknown [12.236.144.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 3FC402173B; Sat, 24 Aug 2019 01:18:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1566609487; bh=6f1HDvkdNDwLdAe/vvH9HQBpuyq4dH6kyBR4+kjmGhA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=dIUqgHq5D66APIvweYh2EI2/hVdqXtCAqI/fqg8W0+Pru8rBrzyCsRUISMGo5rFDG Mam+blmMqhAtFVZ2b391sJi19IA06po4FjVetYgZcSnQk8AI8eL6lsKoWfMCjyVYKa G7HSNmjePA4YgsLuLS+vdKyNVv+ZCLwbzXawxadI= Date: Fri, 23 Aug 2019 21:18:05 -0400 From: Sasha Levin To: Greg KH Cc: Stefan Lippers-Hollmann , linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 5.2 000/135] 5.2.10-stable review Message-ID: <20190824011805.GH1581@sasha-vm> References: <20190822170811.13303-1-sashal@kernel.org> <20190822172619.GA22458@kroah.com> <20190823000527.0ea91c6b@mir> <20190822233847.GB24034@kroah.com> <20190823024248.11e2dac3@mir> <20190823062853.GC1581@sasha-vm> <20190823173627.GA1040@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20190823173627.GA1040@kroah.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Fri, Aug 23, 2019 at 10:36:27AM -0700, Greg KH wrote: >On Fri, Aug 23, 2019 at 02:28:53AM -0400, Sasha Levin wrote: >> On Fri, Aug 23, 2019 at 02:42:48AM +0200, Stefan Lippers-Hollmann wrote: >> > Hi >> > >> > On 2019-08-22, Greg KH wrote: >> > > On Fri, Aug 23, 2019 at 12:05:27AM +0200, Stefan Lippers-Hollmann wrote: >> > > > On 2019-08-22, Greg KH wrote: >> > > > > On Thu, Aug 22, 2019 at 01:05:56PM -0400, Sasha Levin wrote: >> > [...] >> > > > It might be down to kernel.org mirroring, but the patch file doesn't >> > > > seem to be available yet (404), both in the wrong location listed >> > > > above - and the expected one under >> > > > >> > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.2.10-rc1.gz >> > [...] >> > > Ah, no, it's not a mirroring problem, Sasha and I didn't know if anyone >> > > was actually using the patch files anymore, so it was simpler to do a >> > > release without them to see what happens. :) >> > > >> > > Do you rely on these, or can you use the -rc git tree or the quilt >> > > series? If you do rely on them, we will work to fix this, it just >> > > involves some scripting that we didn't get done this morning. >> > >> > "Rely" is a strong word, I can adapt if they're going away, but >> > I've been using them so far, as in (slightly simplified): >> > >> > $ cd patches/upstream/ >> > $ wget https://cdn.kernel.org/pub/linux/kernel/v5.x/patch-5.2.9.xz >> > $ xz -d patch-5.2.9.xz >> > $ wget https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.2.10-rc1.gz >> > $ gunzip patch-5.2.10-rc1.gz >> > $ vim ../series >> > $ quilt ... >> > >> > I can switch to importing the quilt queue with some sed magic (and I >> > already do that, if interesting or just a larger amounts of patches are >> > queuing up for more than a day or two), but using the -rc patches has >> > been convenient in that semi-manual workflow, also to make sure to really >> > get and test the formal -rc patch, rather than something inbetween. >> >> An easy way to generate a patch is to just use the git.kernel.org web >> interface. A patch for 5.2.10-rc1 would be: >> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.2.y&id2=v5.2.9 >> >> Personally this patch upload story sounded to me like a pre-git era >> artifact... > >Given that we no longer do patches for Linus's -rc releases for the past >few years, maybe it is time to move to do the same for the stable >releases to be consistent. Or tarballs? Why do we generate tarballs (and go through kup)? git.kernel.org already does it for us. -- Thanks, Sasha