linux-kernel - Re: stable patch queues and submission

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110916183113.GY10700@zod.bos.redhat.com>
Date:	Fri, 16 Sep 2011 14:31:13 -0400
From:	Josh Boyer <jwboyer@...hat.com>
To:	Greg KH <gregkh@...e.de>
Cc:	andi@...stfloor.org, willy@...a-x.org,
	paul.gortmaker@...driver.com, linux-kernel@...r.kernel.org
Subject: Re: stable patch queues and submission

On Fri, Sep 16, 2011 at 08:23:50PM +0200, Greg KH wrote:
> > Hi All,
> > 
> > With kernel.org being down, the stable@...nel.org list is no longer
> > working.  This leaves me wondering if we should send patches directly to
> > the various stable tree maintainers with [stable] in the prefix and
> > linux-kernel CC'd, or if the stable queues are even being maintained
> > during the outage.
> 
> No, please do not, unless you need something "special", and even then,
> please cc: lkml and the developers so it's not lost.

Would "special" include patches that are backported for longterm
releases?

> > Does anyone have a preference or suggestion on how to continue stable
> > releases until the list comes back?  (I'm assuming 'wait' isn't really a
> > best all around option.)
> 
> Wait and continue to add the marking to your patches, my scripts are
> still running and pulling the patches out and they are going into the
> stable queue just fine.  The queue just isn't public at the moment due
> to kernel.org being out.

That's good to hear, and works for new patches with CC in the commit
log.  I should have been more clear in that I was more curious about
patches that are needed for longterm kernels but the upstream commits
don't directly apply.  They need to be backported and sent somewhere.

josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/