linux-kernel - Re: [ANNOUNCE] linux-staging tree created

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: <20080610225222.GG8397@mit.edu>
Date:	Tue, 10 Jun 2008 18:52:22 -0400
From:	Theodore Tso <tytso@....edu>
To:	Greg KH <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [ANNOUNCE] linux-staging tree created

On Tue, Jun 10, 2008 at 12:05:40PM -0700, Greg KH wrote:
> PURPOSE
> 
> The linux-staging tree was created to hold drivers and filesystems and
> other semi-major additions to the Linux kernel that are not ready to be
> merged at this point in time.  It is here for companies and authors to
> get a wider range of testing, and to allow for other members of the
> community to help with the development of these features for the
> eventual inclusion into the main kernel tree.
> 
> This tree will be included in the daily linux-next builds, and will get
> testing by all users of that tree.

Does this mean that the nature of linux-next is changing?  I thought
the whole point of linux-next was only to have what would be pushed to
Linus in the near future, so we could check for patch compatibility
issues.  For that reason, for example, I don't push the unstable set
of patches in the ext4 tree to linux-next, since they aren't ready for
merging yet in their current form.  

But if linux-staging is going to be pushed to linux-next, doesn't that
violate the ground rules of Linux-next?  Or are we allowing in this
case because these are filesystems and/or device drivers that don't
exist at all in the mainline tree yet?

						- Ted

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