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: <20130821001111.GB5441@roeck-us.net>
Date:	Tue, 20 Aug 2013 17:11:11 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Greg KH <gregkh@...uxfoundation.org>
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:17:43PM -0700, Greg KH wrote:
> 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.
> 
That is not what I mean. I referred to the master branch of the stable
repository, which you normally update to the most recent -rc when you
publish a new -stable release.

> 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.
> 
I would not ask for creating any new branches. The existing ones are good
enough.

> 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.
> 
The master branch of linux-stable.git on kernel.org currently points to
v3.11-rc5. All I asked for is to update it to the latest -rc prior to
accepting patches from this -rc into a stable release.

I am running my test suite on linux-stable:master to have a reference
and comparison against the various -stable branches. As soon as you update
the master branch of linux-stable.git (eg after you push v3.11-rc6 into it),
the test suite will automatically run on it.

Obviously I could track linux-kernel.git itself instead, but there is much more
activity on it and I am really only interested in the most recent tagged version.

Hope that describes it better.

Guenter
--
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/