Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S288112AbSA3Cp4>; Tue, 29 Jan 2002 21:45:56 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S288109AbSA3Cpq>; Tue, 29 Jan 2002 21:45:46 -0500
Received: from kaboom.dsl.xmission.com ([166.70.87.226]:6065 "EHLO
	mail.oobleck.net") by vger.kernel.org with ESMTP id <S288089AbSA3Cpi>;
	Tue, 29 Jan 2002 21:45:38 -0500
Date: Tue, 29 Jan 2002 19:45:36 -0700 (MST)
From: Chris Ricker <kaboom@gatech.edu>
Reply-To: Chris Ricker <kaboom@gatech.edu>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: World Domination Now! <linux-kernel@vger.kernel.org>
Subject: Re: A modest proposal -- We need a patch penguin
In-Reply-To: <Pine.LNX.4.33.0201291641090.1747-100000@penguin.transmeta.com>
Message-ID: <Pine.LNX.4.44.0201291938530.26901-100000@verdande.oobleck.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 Tue, 29 Jan 2002, Linus Torvalds wrote:

> It might not be a bad idea to just make that "mention maintainer at the
> top of the file" the common case.

You snipped the part I was actually interested in.  Let me try again.

We're agreed that the files themselves are the best indicator of where to
route patches, and that MAINTAINERS isn't useful for much besides deciding
who should get IPO offers ;-).  What I'm wondering is where I, as someone
who is listed in some of the Documentation/* stuff as its maintainer, should
be sending patches.  You want a hierarchy, and I think that's perfectly
reasonable, but I have no idea who the layer of the hierarchy between me and
you is....

later,
chris

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