public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Dave Jones <davej@suse.de>
Cc: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
	Steven Walter <srwalter@yahoo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] unchecked request_region's in drivers/net
Date: Thu, 27 Dec 2001 17:14:37 -0700	[thread overview]
Message-ID: <20011227171437.P12868@lynx.no> (raw)
In-Reply-To: <20011227163130.N12868@lynx.no> <Pine.LNX.4.33.0112280043080.15706-100000@Appserv.suse.de>
In-Reply-To: <Pine.LNX.4.33.0112280043080.15706-100000@Appserv.suse.de>; from davej@suse.de on Fri, Dec 28, 2001 at 12:51:56AM +0100

On Dec 28, 2001  00:51 +0100, Dave Jones wrote:
> On Thu, 27 Dec 2001, Andreas Dilger wrote:
> > common directories like drivers/net/foo.c.  In the top-level MAINTAINER
> > file would only be something like "Marcello Tosatti" to cover the
> > entire tree, and e.g. "David Miller" in the net/MAINTAINER, "Al Viro" in
> > the fs/MAINTAINER, "Stephen Tweedie" in fs/ext3/MAINTAINER, etc.
> 
> Indeed, this solves the keeping the list up to date with whats
> in the tree, and has provision for arbitary numbers of METOO:
> fields (Though that could get messy, whats to stop Linus getting bombed
> with a zillion additions from people who just want to get their
> name in a kernel tarball for free). One way could be approval from
> the actual maintainer "Yes, he's sent lots of patches, add him to
> METOO:".

I'd rather avoid having Linus become a human mailing-list administrator.

Rather, the "METOO" section would be handled by just adding a mailing
list address in the relevant MAINTAINER file.  The above examples would
be covered by linux-kernel, linux-net, linux-fsdevel, and ext2-devel.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2001-12-28  0:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-27 20:38 [RFC][PATCH] unchecked request_region's in drivers/net Steven Walter
2001-12-27 22:23 ` Arnaldo Carvalho de Melo
2001-12-27 22:44   ` Dave Jones
2001-12-27 22:51     ` Arnaldo Carvalho de Melo
2001-12-27 23:25     ` James A Sutherland
2001-12-27 23:40       ` Dave Jones
2001-12-28  9:50         ` James A Sutherland
2001-12-28 11:14           ` Dave Jones
2001-12-27 23:31     ` Andreas Dilger
2001-12-27 23:40       ` Arnaldo Carvalho de Melo
2001-12-28  0:11         ` Andreas Dilger
2001-12-28  0:25           ` Arnaldo Carvalho de Melo
2001-12-27 23:51       ` Dave Jones
2001-12-28  0:14         ` Andreas Dilger [this message]
2001-12-28  0:42           ` Alan Cox
2001-12-28 18:34       ` Riley Williams
2001-12-28 18:48         ` Alan Cox
2001-12-28 19:38           ` Rik van Riel
2001-12-28 23:26             ` Alan Cox
2001-12-28 20:48           ` James A Sutherland
2001-12-28 20:34         ` Andreas Dilger
2001-12-28 21:23           ` Riley Williams
2001-12-29 18:21     ` Oliver Xymoron
  -- strict thread matches above, loose matches on Subject: below --
2001-12-28  7:21 Zwane Mwaikambo
2001-12-28 16:29 ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011227171437.P12868@lynx.no \
    --to=adilger@turbolabs.com \
    --cc=acme@conectiva.com.br \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srwalter@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox