mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: "Eric S. Raymond" <esr@thyrsus.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Albert D. Cahalan" <acahalan@cs.uml.edu>,
	Matthew Wilcox <willy@ldl.fc.hp.com>,
	james rich <james.rich@m.cc.utah.edu>,
	linux-kernel@vger.kernel.org, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention?
Date: Fri, 20 Apr 2001 15:23:32 -0600 (MDT)	[thread overview]
Message-ID: <200104202123.f3KLNWSm031572@webber.adilger.int> (raw)
In-Reply-To: <20010420195004.A5510@flint.arm.linux.org.uk> "from Russell King at Apr 20, 2001 07:50:04 pm"

Russell King writes:
> - Secondly, its very easy to miss stuff in the lkml hunk of email each
>   day when you have less than 4 hours to read it and think about it.
>   (note that architecture maintainers have to read mail from their
>   side which may not be on lkml, think about that, think about bug fixes,
>   possible impacts of fixes on other machines, etc etc).  Therefore,
>   copying their email address registered in the MAINTAINER file means
>   that they should not overlook your patch.

One of the issues for contacting each MAINTAINER is that this information
is out-of-line from the actual kernel tree.  The other is that the
description of what a maintainer is actually controlling is somewhat
vague.

How about the following:
- each directory has a MAINTAINERS file which lists parties with a
  vested interest in files in that directory (format is mostly the
  same as current)
- subdirectories which don't have a MAINTAINERS file use the MAINTAINERS
  file of the parent (or grandparent) directory
- each maintainer entry explicitly lists each file/directory that this
  person is interested in, maybe "F: {file | directory} ...".

I'm sure Eric can come up with a simple program to parse the MAINTAINER
file/tree.  If the program takes a kernel-tree relative filename and
spit out the name/email of the relevant maintainer (subsystem and port
specific mailing lists should also be included), that would make the 
job of finding out who to send patches to a whole lot easier.

My one gripe about the MAINTAINERS file is that it still lists Remy
Card as EXT2 maintainer, so we would probably need to do a find on
the whole kernel tree, email each address a list of files that they
"maintain" and wait until they complain, agree, or time out.  Once
the database is up-to-date, it simplifies the job of keeping maintainers
(and other interested parties) in the loop.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

  reply	other threads:[~2001-04-20 21:26 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20  2:36 Matthew Wilcox
2001-04-20  3:00 ` Eric S. Raymond
2001-04-20  3:17   ` Matthew Wilcox
2001-04-20  4:07     ` james rich
2001-04-20  4:19       ` Matthew Wilcox
2001-04-20  4:52         ` Albert D. Cahalan
2001-04-20  5:17           ` Rik van Riel
2001-04-20 13:13           ` [parisc-linux] " Alan Cox
2001-04-20 13:35             ` Eric S. Raymond
2001-04-20 13:43               ` Alan Cox
2001-04-20 13:53                 ` Eric S. Raymond
2001-04-20 14:03                   ` Alan Cox
2001-04-20 14:19                     ` Eric S. Raymond
2001-04-20 14:44                       ` Alan Cox
2001-04-20 14:59                         ` Eric S. Raymond
2001-04-20 15:51                           ` Tom Rini
2001-04-20 16:06                             ` Jeff Garzik
2001-04-20 16:15                               ` Bob McElrath
2001-04-20 16:21                                 ` Matthew Wilcox
2001-04-20 19:00                                   ` Jeff Dike
2001-04-20 18:47                                     ` Matthew Wilcox
2001-04-20 21:55                                       ` Jeff Dike
2001-04-20 18:53                                     ` Jes Sorensen
2001-04-20 16:26                                 ` Jeff Garzik
2001-04-20 16:35                             ` Nicolas Pitre
2001-04-20 16:50                               ` Eric S. Raymond
2001-04-20 19:08                                 ` Russell King
2001-04-21  3:08                                   ` Tom Leete
2001-04-21  8:53                                     ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone rmk
2001-04-20 18:20                               ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? Tom Rini
2001-04-20 18:48                                 ` Nicolas Pitre
2001-04-20 18:55                                   ` Tom Rini
2001-04-20 21:19                                   ` David Woodhouse
2001-04-20 21:24                                     ` Eric S. Raymond
2001-04-20 21:29                                     ` David Woodhouse
2001-04-20 21:35                                       ` Eric S. Raymond
2001-04-20 22:53                                         ` Alan Cox
2001-04-21  0:37                                           ` Eric S. Raymond
2001-04-21 23:39                                             ` Jes Sorensen
2001-04-21 12:32                                           ` David Woodhouse
2001-04-23 21:12                                             ` [patch] fix broken symbols (was Re: OK, let's try ...) Arjan van de Ven
2001-04-20 21:39                                       ` [parisc-linux] Re: OK, let's try cleaning up another nit. Is anyone paying attention? David Woodhouse
2001-04-21  0:24                                         ` Eric S. Raymond
2001-04-20 18:50                           ` Russell King
2001-04-20 21:23                             ` Andreas Dilger [this message]
2001-04-21  0:52                               ` Proposal for better attribution structure Eric S. Raymond
2001-04-20  8:19       ` OK, let's try cleaning up another nit. Is anyone paying attention? David Woodhouse
2001-04-20 19:47     ` Eric S. Raymond
2001-04-20 20:00       ` Matthew Wilcox
2001-04-20 20:13         ` Eric S. Raymond
2001-04-20 20:55       ` Alan Cox
2001-04-21  6:48       ` [parisc-linux] " Grant Grundler
2001-04-21 14:52         ` Eric S. Raymond
2001-04-20 13:08   ` Alan Cox
2001-04-20 13:18     ` Eric S. Raymond
2001-07-29 10:47     ` Riley Williams

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=200104202123.f3KLNWSm031572@webber.adilger.int \
    --to=adilger@turbolinux.com \
    --cc=acahalan@cs.uml.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=esr@thyrsus.com \
    --cc=james.rich@m.cc.utah.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parisc-linux@parisc-linux.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=willy@ldl.fc.hp.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

all inboxes | Powered by JetHome®