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: <20130820231743.GA992@kroah.com>
Date:	Tue, 20 Aug 2013 16:17:43 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	stable <stable@...r.kernel.org>, lwn@....net,
	Hugh Dickins <hughd@...gle.com>,
	Johannes Berg <johannes@...solutions.net>,
	Borislav Petkov <bp@...en8.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Proposed stable release changes

On Tue, Aug 20, 2013 at 04:11:17PM -0700, Guenter Roeck wrote:
> It would be even better if you could find the time to push -rc releases
> into the stable repository before you accept patches into a stable branch.

What do you mean by this?

The git tree?  I could do that, but when I have to drop a patch, it
would cause a mess if I had to always go forwards.

I could do branches for -rc releases, that end up as the
"end-of-the-line", and I create the next .y release on top of the
previous one, not the -rc release.

That's kind of what I do "internally" when I create the -rc releases in
the first place, but I just delete those throw-away trees, and never
push them publicly anywhere.

Does it really help anyone to do this, except for some automated
testing?  Doesn't the -rc patch work good enough for that?

> I am now running my test suite on stable/master, so that would give it
> some time to catch new problems before they make their way into a stable
> branch.

I don't understand what you mean here.

thanks,

greg k-h
--
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/