LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] How to (automatically) find the correct maintainer(s)
Date: Mon, 15 Jan 2007 21:21:15 +0100	[thread overview]
Message-ID: <45ABE23B.6010405@student.ltu.se> (raw)
In-Reply-To: <45ABDE79.7050706@citd.de>

Matthias Schniedermeyer wrote:
> Richard Knutsson wrote:
>   
>> Stefan Richter wrote:
>>
>>     
>>> On 15 Jan, Matthias Schniedermeyer wrote:
>>>  
>>>
>>>       
>>>> 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?
>>>>     
>>>>         
>>> Or, "click here to say 'it does not work'"?
>>>
>>> My rhetorical question wasn't about what it is intended for, but what
>>> people would think it was intended for if it was there.
>>>
>>>   
>>>       
>> I think it could be practical to have an easy access to whom is
>> responsible for a driver and which mailinglist its development is
>> addressed to, both for people interested in helping develop the driver
>> and those who got an error (or fan-mail :).
>>
>>     
>>>> 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.
>>>>     
>>>>         
>>> Seems more like what you actually want to have there is links to users'
>>> mailinglists or forums.
>>>
>>> When this thread started, it was about assisting authors in submitting
>>> patches.
>>>
>>>   
>>>       
>> Yes, this is a bit out of scope, but just realized a simple way to
>> implement it if using the CONFIG_FLAG-approach, just "grep" after the
>> flag, under which the user hit the "Maintainer"-button, in the
>> MAINTAINER-file. Also, I think this solves the handler-problem since an
>> entry can have multiple CONFIG_FLAG's stated.
>>
>> I don't think we should add the maintainer-entries directly in Kconfig,
>> as you Stefan stated, because it is for configure the kernel. With the
>> above approach, it will just require minor fixes in the "make *config"
>> to handle it.
>>     
>
> But how do you suppose the user gets the CONFIG_-String, which the user
> then could for searching?
>
> I'd say only a small percentage of hardcore-users would use the
> .config-file directly, the others would deviate over *config, so i'd say
> if the MAINTAINERS-data is integrated into Kconfig it's the perfect(tm)
> 90% solution.
>
> OTOH you could just teach the *config to lookup a MAINTAINERS-entry when
> all they are properly flagged.
>   
Oh no, did'n mean like that. All entries in the Kconfig has a "config 
CONFIG_FLAG" (of course ;) ) and so *config "knows" which flag to search 
for (if added to MAINTAINERS, that is).


  reply	other threads:[~2007-01-15 20:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13 16:30 Richard Knutsson
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 [this message]
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=45ABE23B.6010405@student.ltu.se \
    --to=ricknu-0@student.ltu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ms@citd.de \
    --cc=stefanr@s5r6.in-berlin.de \
    --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).