Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S130768AbRDWFEH>; Mon, 23 Apr 2001 01:04:07 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S130820AbRDWFD5>; Mon, 23 Apr 2001 01:03:57 -0400
Received: from snowbird.megapath.net ([216.200.176.7]:12554 "EHLO
	megapathdsl.net") by vger.kernel.org with ESMTP id <S130768AbRDWFDt>;
	Mon, 23 Apr 2001 01:03:49 -0400
Date: Sun, 22 Apr 2001 21:59:32 -0700 (PDT)
From: Miles Lane <miles@megapathdsl.net>
To: "David S. Miller" <davem@redhat.com>
cc: Russell King <rmk@arm.linux.org.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: All architecture maintainers: pgd_alloc()
In-Reply-To: <15075.45847.624767.960502@pizda.ninka.net>
Message-ID: <Pine.LNX.4.30.0104222156180.6639-100000@aerie.megapathdsl.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Sun, 22 Apr 2001, David S. Miller wrote:

<snip>

> My main point is that for changes like this, sending stuff to Alan
> first is often an ineffective mechanism.  If someone were to reply to
> this "Linus is hard to push changes too, or takes too long" my reply
> is "if this is really the problem, should the burdon should be
> entirely placed on Alan's shoulders?"

Perhaps Alan could speak to this.

Alan, could you delegate any of this work?  Is it feasible to
have you redirect some portion of the patch analysis and acceptance
load to another person, other than Linus?  Obviously, if the rate
of patch flow increases significantly, others will need to get
involved more closely with the patch acceptance process.

	Miles

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