From: Roland Dreier <rdreier@cisco.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Linux v2.6.27-rc1
References: <alpine.LFD.1.10.0807281956030.3334@nehalem.linux-foundation.org>
	<200807290927.12101.jbarnes@virtuousgeek.org>
	<alpine.LFD.1.10.0807290945030.3334@nehalem.linux-foundation.org>
Date: Tue, 29 Jul 2008 10:31:31 -0700
In-Reply-To: <alpine.LFD.1.10.0807290945030.3334@nehalem.linux-foundation.org>
	(Linus Torvalds's message of "Tue, 29 Jul 2008 09:59:18 -0700 (PDT)")
Message-ID: <adafxps4mx8.fsf@cisco.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 789
Lines: 16

 >    That may not sound like much, but it's enough to make me worry about 
 >    'next'. I worry that 'it has been in next' has become a code-word for 
 >    "pull this, because it's good", and I'm not at all convinced that 
 >    'next' sees any real critical checking.

I've been mentioning that my trees have been in next as code for, "I
don't think this should break the build or clash too badly with anything
else."  And next has been useful to me on several occasions for catching
that sort of problem before things hit mainline.

 - R.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/