mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: linux-next@vger.kernel.org
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Ingo Molnar <mingo@elte.hu>, Greg KH <greg@kroah.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: linux-next: the purge :-)
Date: Thu, 8 May 2008 11:21:30 +1000	[thread overview]
Message-ID: <20080508112130.fd574b50.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

Hi all,

Having published my expectations of what should be in linux-next, I am
no implementing what I think is what I said.  :-)

This is open to discussion (including suggestions about other trees).

The following trees are being excluded from today because I think that
they contain changes that:
	- have not been published/reviewed/tested sufficiently
	- are not currently intended for 2.6.26 or 2.6.27.
(not all reasons apply to all trees).  Please don't take offense, I am
just trying to obey my own guidelines.

ldp
x86_latest
sched_latest

Ingo, I assume that things will migrate from {x86,sched} latest to
for-akpm (for-next?) over time.  Greg, you might consider setting up a
subset (currently probably empty) of the ldp tree for drivers that are
readier for integration.

As an aside, the kbuild tree is still dropped for today since Sam is not
in a position to fix stuff until the weekend and the wireless tree is
dropped today because it can not be fetched.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2008-05-08  1:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  1:21 Stephen Rothwell [this message]
2008-05-08  1:56 ` John W. Linville
2008-05-08  4:33   ` Stephen Rothwell
2008-05-08  4:27 ` Greg KH
2008-05-08  6:27   ` Adrian Bunk
2008-05-08 22:04     ` Greg KH
2008-05-09  1:16       ` Stephen Rothwell
2008-05-09  3:44         ` Greg KH
2008-05-09  4:18           ` Greg KH
2008-05-09  6:10             ` Stephen Rothwell
2008-05-08  9:55 ` Thomas Gleixner
2008-05-08 10:46   ` Stephen Rothwell

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=20080508112130.fd574b50.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®