[lkml]   [2008]   [Jul]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC] MAINTAINERS service, was: Re: alphabetic ordering of MAINTAINERS
Krzysztof Halasa wrote:
> Stefan Richter <> writes:
>> We expect submissions to based on something more recent than 2.6.12.
> Unfortunately we can't enforce that. People are working with old
> kernels (think of heavily-modified vendor trees), people send patches
> against old kernels, and we accept such patches (if it makes sense,
> of course).

If I get such patches and can apply them without /very/ much work, I
gladly take them of course too.

But these are not the people anyway to which this maintainers lookup
service would be targeted to. As I see it, the people who want such a
service are those who frequently send patches for various different
areas of the kernel. And these people don't work with 2.6.12.

(OTOH, occasional posters who don't even check if their patch would
apply to a newer kernel too before they post it will probably also have
less interest in figuring out the 100% optimum To: and Cc: list for
their submission. A "tell me a list of mail addresses; whatever you
give me, I am not really interested in the particulars" service would
not be an appropriate tool for these people.)

>> Your patch service however...
>> ...already exists. Check the "L:" entries in MAINTAINERS.
> Nice joke.

Not at all. These are the forums where patches can be discussed in more
detail because knowledgeable people are subscribed there. You also have
archives which you can query for patch postings and their discussions.

What you don't get is of course a unified "look and feel". Some list
archives are crap, some lists are subscriber-only, some kernel areas are
not covered by a special list. But the latter problem won't really go
away with the proposed maintainers lookup service.
Stefan Richter
-=====-==--- -=== --===

 \ /
  Last update: 2008-07-07 21:21    [W:3.651 / U:0.000 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site