public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: landley@trommello.org
Cc: Andreas Dilger <adilger@clusterfs.com>,
	karim@opersys.com, linux-kernel@vger.kernel.org,
	boissiere@nl.linux.org
Subject: Re: Crunch time -- Final merge candidates for 3.0 (the list).
Date: Mon, 21 Oct 2002 01:25:09 -0700	[thread overview]
Message-ID: <3DB3B9E5.6452076B@digeo.com> (raw)
In-Reply-To: 200210202147.23712.landley@trommello.org

Rob Landley wrote:
> 
> Query: is the stuff in -mm guaranteed to make it into Linus's tree?

Nope.

It's mainly there for the other VM/MM/IO developers to
integrate against.

Also for getting their more experimental work more testing and exposure.  

Also for getting external testing of the performance work
which is going into it.

Also for maintainers of other architectures to pick up breakage
before things break.

I prefer to only send things which I understand and have tested.
So that excludes, say, dcache-rcu and the EA/xattr patches.  I
did send ext3-htree, but it had big "I haven't tested this" labels
all over it.

  parent reply	other threads:[~2002-10-21  8:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-20 23:49 Crunch time -- Final merge candidates for 3.0 (the list) Rob Landley
2002-10-21  5:44 ` Hans Reiser
2002-10-21  6:03 ` Karim Yaghmour
2002-10-21  1:37   ` Rob Landley
2002-10-21  6:43     ` Andreas Dilger
2002-10-21  2:47       ` Rob Landley
2002-10-21  8:05         ` Andreas Dilger
2002-10-21  8:25         ` Andrew Morton [this message]
2002-10-21 11:56 ` Alan Cox
2002-10-21 12:23 ` Denis Vlasenko
2002-10-21  3:00   ` Rob Landley

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=3DB3B9E5.6452076B@digeo.com \
    --to=akpm@digeo.com \
    --cc=adilger@clusterfs.com \
    --cc=boissiere@nl.linux.org \
    --cc=karim@opersys.com \
    --cc=landley@trommello.org \
    --cc=linux-kernel@vger.kernel.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