linux-kernel - Re: Announce: Linux-next (Or Andrew's dream :-))

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: <20080214232229.f7bdc6ac.sfr@canb.auug.org.au>
Date:	Thu, 14 Feb 2008 23:22:29 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Theodore Tso <tytso@....edu>,
	Trond Myklebust <trond.myklebust@....uio.no>,
	Arjan van de Ven <arjan@...radead.org>,
	Greg KH <greg@...ah.com>, LKML <linux-kernel@...r.kernel.org>,
	linux-next@...r.kernel.org, linux-arch@...r.kernel.org,
	Linus <torvalds@...ux-foundation.org>
Subject: Re: Announce: Linux-next (Or Andrew's dream  :-))

Hi Russell,

On Thu, 14 Feb 2008 08:14:05 +0000 Russell King <rmk+lkml@....linux.org.uk> wrote:
>
> On Tue, Feb 12, 2008 at 10:57:16PM +1100, Stephen Rothwell wrote:
> > We need to ask Linus to promise that he will pull the stable branch from
> > linux-next first in the merge window.  For that to happen, I would expect
> > that Linus would also review and sign off (or ack) these commits to the
> > linux-next tree.
> 
> Changing the commits in git in anyway changes their ID, which has the
> same effects as a rebase.

Correct.

> With this idea, Linus only has two choices:
> 
> 1. pull the entire set of linux-next changes whether he likes them or not,
>    because he's going to get them either from the linux-next tree or someone
>    elses tree which is based upon that.
> 
> 2. don't pull the changes, nor anyone elses tree if he hates the changes
>    in linux-next.
> 
> So really, Linus needs to ack the changes _before_ they go into linux-next.

This is exactly what I suggested (or meant to) *except* that I want it to
only apply to the stable branch.  I intend that the stable branch of
linux-next will never be rebased and so is suitable for others to base
their trees off.  The master branch will be continually rebased as the
subsystem trees change over time.

Originally, I assumed the stable branch would be for our "usual" API
changes, but it appears we are not having any more of those. :-)  However,
I see an argument for attempting to stabilise possible conflicting
changes get Linus' review/ack and add them to the stable branch.

Linus suggested that such changes should go into an independent tree that
everyone could pull into their trees with the full confidence that that
tree would be merged into Linus' tree when the merge window opens.  I am
suggesting that that tree be the stable branch of linux-next.

I know I haven't thought through all the consequences of this, so
discussion is encouaged.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped