Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S129183AbRBVMY5>; Thu, 22 Feb 2001 07:24:57 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S129306AbRBVMYr>; Thu, 22 Feb 2001 07:24:47 -0500
Received: from router-100M.swansea.linux.org.uk ([194.168.151.17]:14097 "EHLO
	the-village.bc.nu") by vger.kernel.org with ESMTP
	id <S129183AbRBVMY2>; Thu, 22 Feb 2001 07:24:28 -0500
Subject: Re: Linux-2.4.2
To: Werner.Almesberger@epfl.ch (Werner Almesberger)
Date: Thu, 22 Feb 2001 12:27:45 +0000 (GMT)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
        linux-kernel@vger.kernel.org (Kernel Mailing List)
In-Reply-To: <20010222131407.A19635@almesberger.net> from "Werner Almesberger" at Feb 22, 2001 01:14:07 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <E14VuqZ-00043G-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

> 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) ?

Im trying to push stuff to Linus in a reasonably controlled way. That tends to
mean the less important or more obscure hardware comes later

Alan

-
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/