From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Will Newton" Subject: Re: [ANNOUNCE] linux-staging tree created Date: Wed, 11 Jun 2008 11:45:55 +0100 Message-ID: <87a5b0800806110345v77529fc8r591f2fb4c95b5bdf@mail.gmail.com> References: <20080610190540.GA25066@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from yw-out-2324.google.com ([74.125.46.30]:31225 "EHLO yw-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753896AbYFKKqA (ORCPT ); Wed, 11 Jun 2008 06:46:00 -0400 Received: by yw-out-2324.google.com with SMTP id 9so1883347ywe.1 for ; Wed, 11 Jun 2008 03:45:55 -0700 (PDT) In-Reply-To: <20080610190540.GA25066@kroah.com> Content-Disposition: inline Sender: linux-next-owner@vger.kernel.org List-ID: To: Greg KH Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org, kernel-janitors@vger.kernel.org, linux-next@vger.kernel.org, Stephen Rothwell On Tue, Jun 10, 2008 at 8:05 PM, Greg KH wrote: > This tree will be included in the daily linux-next builds, and will get > testing by all users of that tree. > > The rules of what can be included here is as follows: > - the code must be released under a Linux kernel-compatible > license > - the goal of the developers must be to merge this code into the > main kernel tree in the near future, but not for the next > kernel release. > - the code must build properly on the x86 platform > - this is not a tree for bugfixes or rewrites of existing kernel > code, this should be for new features, drivers, and > filesystems. > - the patches included must detail exactly what is needed to be > completed in order for them to be included into the main > kernel tree. > - there must be some email address associated with the patch > that can be used for bug reporting and questions about > cleanups and testing the code. > > What this tree is not: > - it is not a place to dump features that are being actively > developed by a community of people (reiserfs4 for example.) > - it is not a place to dump code and then run away, hoping that > someone else will do the cleanup work for you. While there > are developers available to do this kind of work, you need to > get someone to agree to "babysit" the code. Would the linux-staging tree be an appropriate place to merge a new architecture? Or would that be too large a change and should go via its own tree?