LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Richard Knutsson <ricknu-0@student.ltu.se>
To: linux-kernel@vger.kernel.org
Subject: [RFC] How to (automatically) find the correct maintainer(s)
Date: Sat, 13 Jan 2007 17:30:39 +0100	[thread overview]
Message-ID: <45A9092F.7060503@student.ltu.se> (raw)

Hello all

Would like to come with a suggestion I have been wondering about for a 
while, why not add the config-flag, used in Kconfig/Makefile in the 
MAINTAINERS-file?

By doing this, there would not be any confusion who to send a patch, 
since all "files" is defined under a flag, right? (when it is a 
header-file, it can be grep'ed on the c-files and from the hit find the 
flag)

So, with a MAINTAINERS-entry like:

SUPERCOOL ALPHA CARD

P:	Clark Kent
M:	superman@krypton.kr
L:	some@thing.com
C:	SUPER_A
S:	Maintained
(C: for CONFIG. Any better idea?)

then if someone changes a file who are built with CONFIG_SUPER_A, can 
easily backtrack it to the correct maintainer(s). And because there is 
no question how to find the correct maintainer, a script can do it for 
us. This is something that would be really useful for Kernel-Janitors 
when doing big cleanups all over the kernel (see ex pci_module_init to 
pci_register_driver and standardize the tree to use macros from 
include/linux/kernel.h).
By this, I believe trivial patch-series would be reduced from the lkml 
when they can automatically be sent to the maintainer (and maybe 
specified mailing-list).

My first idea was to use the pathway and define that directories above 
the specified (if not specified by another) would fall to the current 
maintainer. It would work, but requires that all pathways be specified 
at once, or a few maintainers with "short" pathways would get much of 
the patches (and it is not as correct/easy to maintain as looking for 
the CONFIG_flag).


Any thoughts on this is very much appreciated (is there any flaws with 
this?).

Richard Knutsson


             reply	other threads:[~2007-01-13 16:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13 16:30 Richard Knutsson [this message]
2007-01-13 17:16 ` Stefan Richter
2007-01-13 19:18   ` Richard Knutsson
2007-01-13 20:15     ` Stefan Richter
2007-01-13 23:33       ` Richard Knutsson
2007-01-14  1:00         ` Stefan Richter
2007-01-14  1:02           ` Stefan Richter
2007-01-14 21:28           ` Richard Knutsson
2007-01-14 22:44             ` Stefan Richter
2007-01-15 18:39               ` Richard Knutsson
2007-01-15 20:06                 ` Stefan Richter
2007-01-13 20:03 ` Matthias Schniedermeyer
2007-01-13 23:41   ` Richard Knutsson
2007-01-14  0:04     ` Matthias Schniedermeyer
2007-01-14 21:42       ` Richard Knutsson
2007-01-14 23:04         ` Stefan Richter
2007-01-15  0:01           ` Matthias Schniedermeyer
2007-01-15  0:43             ` Stefan Richter
2007-01-15 18:01               ` Richard Knutsson
2007-01-15 20:05                 ` Matthias Schniedermeyer
2007-01-15 20:21                   ` Richard Knutsson
2007-01-14 23:36         ` Matthias Schniedermeyer
2007-01-22 19:56 ` Andrew Morton

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=45A9092F.7060503@student.ltu.se \
    --to=ricknu-0@student.ltu.se \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [RFC] How to (automatically) find the correct maintainer(s)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).