linux-kernel - Re: Proposed stable release changes

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: <20130822085721.GA16792@nazgul.tnic>
Date:	Thu, 22 Aug 2013 10:57:21 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Tony Luck <tony.luck@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Stephen Warren <swarren@...dotorg.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	stable <stable@...r.kernel.org>, lwn@....net,
	Guenter Roeck <linux@...ck-us.net>,
	Hugh Dickins <hughd@...gle.com>,
	Johannes Berg <johannes@...solutions.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Proposed stable release changes

On Wed, Aug 21, 2013 at 01:54:01PM -0700, Tony Luck wrote:
> On Wed, Aug 21, 2013 at 1:00 PM, Borislav Petkov <bp@...en8.de> wrote:
> > We don't want to run daily snapshots of your tree though, right? Only
> > -rcs because the daily states are kinda arbitrary and they can be broken
> > in various ways. Or are we at a point in time where we can amend that
> > rule?
> 
> If *nobody* runs daily snapshots - then problems just sit latent all week until
> the -rc is released and people start testing. Doesn't sound optimal.
> 
> Running daily git snapshots can be "exciting" during the merge window. But
> I rarely see problems running a random build after -rc1.  If you are still
> running that ancient 3.11-rc6 released on Sunday - then you are missing out
> on 28 commits worth of goodness since then :-)

Damn, I'm such a l0z3r!
--
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/