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

Stefan Richter wrote:
> On 14 Jan, Richard Knutsson wrote:
>   
>> Stefan Richter wrote:
>>     
>>> May I remind that whoever uses scripts to figure out contacts should
>>> better double-check what the script found out for him.
>>>       
> [...]
>   
>> During development, that's a given. But I would hope that when its more 
>> stable it will always find the right answer or no answer at all (if 
>> there is errors in ex MAINTAINERS, even the human will bother the receiver)
>>     
>
> Note, if people build scripts which look up contacts, I hope they don't
> become careless and forget to search elsewhere for proper contacts if
> _no_ contact was found automatically.
>   
Maybe the script may print out some pointers for such a case ;)
> [...]
>   
>>> It is already somewhat
>>> costly to backtrack .c files from .o files from config options, but
>>> considerably more so with .h files.
>>>
>>>       
>> I think it is to early to be thinking about what is easier, first a 
>> "algorithm" that does what we want is needed, then I'm more then happy 
>> to write a script/program for it :)
>> Costly?? It is even simple in bash:
>> C_FILE=${O_FILE/'.o'/'.c'}
>>     
>
> When I wrote "somewhat costly" I didn't refer to a 1:1 mapping between
> .c and .o. That's not what it takes. I mostly referred to having to
> implement a parser for parts of the Linux Makefile language. On the
> bright side, the more indirection you introduce, the less people will
> write their own scripts and the less scripts with bugs will be out
> there. :-)
>
>   
Oh, yes so it is. But I don't think it will be too much. But do you have 
any objections on the last proposal (to include "I:"), otherwise I 
thinking of trying to implement it (thinking of Perl, any reason to not 
do so?) to see if it can stand real usage.

Hope so (on bugs that is, always fun with scripts) :)
> [...]
>   
>> (I: for "include". Btw, what is F: standing for? Is it instead of P:?)
>>     
> [...]
>
> Doesn't need to be F. "Files" happens to start with F.
>   
Doh, was in the track of "pathway" or such...


  reply	other threads:[~2007-01-15 18:37 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 [this message]
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=45ABCA64.6000000@student.ltu.se \
    --to=ricknu-0@student.ltu.se \
    --cc=linux-kernel@vger.kernel.org \
    --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).