[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45AAC44D.808@citd.de>
Date: Mon, 15 Jan 2007 01:01:17 +0100
From: Matthias Schniedermeyer <ms@...d.de>
To: Stefan Richter <stefanr@...6.in-berlin.de>
Cc: Richard Knutsson <ricknu-0@...dent.ltu.se>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC] How to (automatically) find the correct maintainer(s)
Stefan Richter wrote:
> On 14 Jan, Richard Knutsson wrote:
>
>>(Really liked the idea to have a "Maintainer"-button
>>next to "Help" in *config)
>
>
> Rhetorical question: What will this button be used for?
Having "all(tm)" information of something in one place?
Help-Text and Dependencies/Selects are already there.
I think adding the Maintainers-data is more or less a logical next step.
It's not always clear from the MAINTAINERS-file who is the right person
for what. Especially as it is a rather large text-file with only
mediocre search-friendlieness. It's a 3.5 K-lines file!
So when you know that you have a problem with drivers X, wouldn't it be
great if you could just "go to" the driver in *config and see not only
the Help-Text but the Maintainers-Data also.
And you can place "Fallback"-Maintainers-Data on Tree-Parents, for the
cases where you only can pinpoint a area, like when you have a problem
with a USB-device.
I can ask a rhetorical question too:
Why not go back to Config.help. Having a huge X K-Lines file with
everything in one file can't be that bad. It worked before!
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists