From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: ground rules
Date: Fri, 14 Aug 2009 08:07:59 -0400 [thread overview]
Message-ID: <20090814120759.GA2650@tuxdriver.com> (raw)
In-Reply-To: <20090814180246.9ac3e78e.sfr@canb.auug.org.au>
On Fri, Aug 14, 2009 at 06:02:46PM +1000, Stephen Rothwell wrote:
> [This email has been bcc'd to all the current contributors to
> linux-next. No response is required unless you have some issue with the
> following.]
>
> Thanks for being a participant of linux-next. I have been asked by my
> employer to send you this e-mail summarizing these "ground rules" for the
> project:
>
> The linux-next integration testing is not a judgment of your code. The
> purpose of linux-next is for integration testing and to lower the impact
> of conflicts between subsystems in the next merge window.
>
> You need to ensure that the patches/commits in your tree/series have been:
> * submitted under GPL v2 (or later) and include the Contributor's
> Signed-off-by,
> * posted to the relevant mailing list,
> * reviewed by you (or another maintainer of your subsystem tree),
> * successfully unit tested, and
> * destined for the current or next Linux merge window.
>
> Basically, this should be just what you would send to Linus (or ask him
> to fetch). It is allowed to be rebased if you deem it necessary.
ACK (if that helps!)
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2009-08-14 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 8:02 linux-next: ground rules Stephen Rothwell
2009-08-14 12:07 ` John W. Linville [this message]
2009-08-14 13:56 ` James Bottomley
2009-08-14 15:16 ` Stephen Rothwell
2009-08-14 15:19 ` James Bottomley
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=20090814120759.GA2650@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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