Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S129143AbRBVMPH>; Thu, 22 Feb 2001 07:15:07 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S129183AbRBVMOr>; Thu, 22 Feb 2001 07:14:47 -0500
Received: from lsb-catv-1-p021.vtxnet.ch ([212.147.5.21]:64265 "EHLO
	almesberger.net") by vger.kernel.org with ESMTP id <S129143AbRBVMOf>;
	Thu, 22 Feb 2001 07:14:35 -0500
Date: Thu, 22 Feb 2001 13:14:07 +0100
From: Werner Almesberger <Werner.Almesberger@epfl.ch>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.4.2
Message-ID: <20010222131407.A19635@almesberger.net>
In-Reply-To: <20010221211330.A21010@cadcamlab.org> <E14Vt3p-0003rp-00@the-village.bc.nu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E14Vt3p-0003rp-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Feb 22, 2001 at 10:33:19AM +0000
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Alan Cox wrote:
> I think the key word is actually probably 'predictability'. The Linus tree
> is conservative. (IMHO too conservative and probably in his not conservative
> enough 8))

Hmm, given that there are several patches in your tree that never seem
to make it to Linus' tree, would it make sense to flag patches that
should go into 2.4 as "Not for Alan; Linus _please_ pick it up" (and to
keep on pushing until Linus does) ?

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, ICA, EPFL, CH           Werner.Almesberger@epfl.ch /
/_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
-
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/