From: "Will Newton" <will.newton@gmail•com>
To: Greg KH <greg@kroah•com>
Cc: linux-kernel@vger•kernel.org, devel@linuxdriverproject•org,
kernel-janitors@vger•kernel.org, linux-next@vger•kernel.org,
Stephen Rothwell <sfr@canb•auug.org.au>
Subject: Re: [ANNOUNCE] linux-staging tree created
Date: Wed, 11 Jun 2008 11:45:55 +0100 [thread overview]
Message-ID: <87a5b0800806110345v77529fc8r591f2fb4c95b5bdf@mail.gmail.com> (raw)
In-Reply-To: <20080610190540.GA25066@kroah.com>
On Tue, Jun 10, 2008 at 8:05 PM, Greg KH <greg@kroah•com> 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?
next prev parent reply other threads:[~2008-06-11 10:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 19:05 [ANNOUNCE] linux-staging tree created Greg KH
2008-06-10 19:06 ` linux-staging status for June 10, 2008 Greg KH
2008-06-10 22:52 ` [ANNOUNCE] linux-staging tree created Theodore Tso
2008-06-10 23:05 ` Greg KH
2008-06-11 0:07 ` Felipe Balbi
2008-06-11 3:28 ` Greg KH
2008-06-11 1:05 ` Nigel Cunningham
2008-06-11 3:29 ` Greg KH
2008-06-11 4:00 ` Nigel Cunningham
2008-06-11 16:24 ` Greg KH
2008-06-11 4:03 ` Template of what you're after? (Was [ANNOUNCE] linux-staging tree created) Nigel Cunningham
2008-06-11 16:23 ` Greg KH
2008-06-11 9:27 ` [ANNOUNCE] linux-staging tree created Benny Halevy
2008-06-11 9:50 ` Boaz Harrosh
2008-06-11 9:58 ` Felipe Balbi
2008-06-11 16:25 ` Greg KH
2008-06-11 17:43 ` Boaz Harrosh
2008-06-11 16:25 ` Greg KH
2008-06-11 10:45 ` Will Newton [this message]
2008-06-11 16:26 ` Greg KH
2008-06-12 11:37 ` Will Newton
2008-06-12 23:54 ` Greg KH
2008-06-13 14:14 ` Luis R. Rodriguez
2008-06-13 14:33 ` John W. Linville
2008-06-13 15:51 ` Luis R. Rodriguez
[not found] ` <20080613143328.GA16506-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-14 0:28 ` Greg KH
[not found] ` <43e72e890806130714k535b041evaf750209ea492c47-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-14 0:27 ` Greg KH
2008-06-17 12:51 ` Pavel Machek
2008-07-02 23:11 ` Greg KH
2008-07-14 2:50 ` Jike Song
2008-07-14 2:56 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5b0800806110345v77529fc8r591f2fb4c95b5bdf@mail.gmail.com \
--to=will.newton@gmail$(echo .)com \
--cc=devel@linuxdriverproject$(echo .)org \
--cc=greg@kroah$(echo .)com \
--cc=kernel-janitors@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox