From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: first tree
Date: Tue, 19 Feb 2008 00:15:26 +1100 [thread overview]
Message-ID: <20080219001526.bdb57549.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4d8e3fd30802180311u1f216fe9va916e797db10af12@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
Hi Paolo,
On Mon, 18 Feb 2008 12:11:33 +0100 "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com> wrote:
>
> I would like to update the "The development process" section in
> Documentation/HOWTO including some information about the linux-next tree.
>
> I understand what it's including but I didn't get how it will fit in
> the process.
> Is Linus going to pull from that tree as soon as we reach -rc0 or this
> is just a tree
> used for testing what will be pushed to Linus as soon as the two weeks
> merge window
> open?
The intention is the latter. I hope to help people sort out some of the
conflicts and cross subsystem issues before we get into the merge window
and the code gets into Linus' tree.
Andrew Morton also hopes that the linux-next tree may get more testing
that the -mm tree did if we can stop it having to many regressions by
only including the less experimental code that is destined for the next
kernel release.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-02-18 13:15 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 13:35 Stephen Rothwell
2008-02-14 14:06 ` Jiri Kosina
2008-02-14 14:34 ` Stephen Rothwell
2008-02-14 14:45 ` Rafael J. Wysocki
2008-02-14 15:00 ` Stephen Rothwell
2008-02-14 15:25 ` Martin Schwidefsky
2008-02-14 21:48 ` Stephen Rothwell
2008-02-14 15:49 ` Paul Mundt
2008-02-14 21:58 ` Stephen Rothwell
2008-02-14 15:54 ` Dave Kleikamp
2008-02-14 22:01 ` Stephen Rothwell
2008-02-15 4:58 ` Len Brown
2008-02-15 6:19 ` Stephen Rothwell
2008-02-14 16:04 ` Andy Whitcroft
2008-02-20 14:23 ` Stephen Rothwell
2008-02-20 16:47 ` Randy Dunlap
2008-02-22 0:07 ` Frank Seidel
2008-02-22 0:12 ` Randy Dunlap
2008-02-22 0:22 ` Harvey Harrison
2008-02-22 5:31 ` Frank Seidel
2008-02-22 0:15 ` Greg KH
2008-02-22 5:33 ` Frank Seidel
2008-02-22 0:28 ` Stephen Rothwell
2008-02-22 5:41 ` Frank Seidel
2008-02-22 5:55 ` Stephen Rothwell
2008-02-14 17:38 ` Mauro Carvalho Chehab
2008-02-14 22:24 ` Stephen Rothwell
2008-02-18 16:07 ` Mauro Carvalho Chehab
2008-02-14 18:29 ` Yinghai Lu
2008-02-14 18:39 ` Benny Halevy
2008-02-14 20:20 ` Greg KH
2008-02-14 20:50 ` Sam Ravnborg
2008-02-14 23:52 ` Stephen Rothwell
2008-02-14 23:31 ` Stephen Rothwell
2008-02-14 20:23 ` Sam Ravnborg
2008-02-14 23:35 ` Stephen Rothwell
2008-02-14 21:03 ` Jeff Garzik
2008-02-14 21:05 ` Jeff Garzik
2008-02-14 21:26 ` James Bottomley
2008-02-14 21:45 ` Jeff Garzik
2008-02-14 23:58 ` Stephen Rothwell
2008-02-14 22:27 ` Trond Myklebust
2008-02-15 0:33 ` Stephen Rothwell
2008-02-15 21:00 ` J. Bruce Fields
2008-02-16 15:37 ` Stephen Rothwell
2008-02-14 23:17 ` David Chinner
2008-02-15 0:50 ` Stephen Rothwell
2008-02-15 1:10 ` David Chinner
2008-02-15 2:14 ` Stephen Rothwell
2008-02-15 8:33 ` Bryan Wu
2008-02-16 15:33 ` Stephen Rothwell
2008-02-17 2:23 ` Robin Getz
2008-02-17 5:33 ` Stephen Rothwell
2008-02-16 15:13 ` Stefan Richter
2008-02-16 15:40 ` Stephen Rothwell
2008-02-17 19:09 ` Mark M. Hoffman
2008-02-17 23:27 ` Stephen Rothwell
2008-02-18 8:04 ` Artem Bityutskiy
2008-02-18 8:29 ` Stephen Rothwell
2008-02-18 11:11 ` Paolo Ciarrocchi
2008-02-18 13:15 ` Stephen Rothwell [this message]
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=20080219001526.bdb57549.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
/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
all inboxes | Powered by JetHome®