mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>,
	"Oliver Neukum" <oliver@neukum.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"David Woodhouse" <dwmw2@infradead.org>
Subject: Re: [RFC] MAINTAINERS service, was: Re: alphabetic ordering of MAINTAINERS
Date: Tue, 08 Jul 2008 00:37:55 +0200	[thread overview]
Message-ID: <m37ibxl3r0.fsf@maximus.localdomain> (raw)
In-Reply-To: <48726BF6.8020308@s5r6.in-berlin.de> (Stefan Richter's message of "Mon\, 07 Jul 2008 21\:18\:14 +0200")

Stefan Richter <stefanr@s5r6.in-berlin.de> writes:

>> 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.

They, too. Why not?

> As I see it, the people who want such a
> service are those who frequently send patches for various different
> areas of the kernel.

Sure, they too.

> (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.

And less skills. Though they would manage a single patch submission
address I guess.

>  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.)

I think it would. Why not?

> 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.

Same here, except that it would be easier = "faster" and/or
"possible". "Faster" for regular kernel contributors and "possible"
for many occasional ones.

> 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.

Not the most important points IMHO but yes, that too.

> But the latter problem won't
> really go away with the proposed maintainers lookup service.

Well, I think it should. Why not?
I don't say we replace mailing lists, far from it.
I expect mailing lists to be subscribed to the service.

Come on, the theory looks good but the thing needs to be created and
_that_ may be the weak spot :-)
-- 
Krzysztof Halasa

  reply	other threads:[~2008-07-07 22:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04  6:34 Uwe Kleine-König
2008-07-04  6:39 ` Sam Ravnborg
2008-07-04  6:41   ` Uwe Kleine-König
2008-07-04  6:52 ` Oliver Neukum
2008-07-04  6:57   ` Uwe Kleine-König
2008-07-04  8:59     ` Paul Mundt
2008-07-04  9:10       ` Uwe Kleine-König
2008-07-04 12:07         ` Alan Cox
2008-07-04 14:02           ` Uwe Kleine-König
2008-07-04 12:02   ` Bernd Petrovitsch
2008-07-04 12:06     ` Oliver Neukum
2008-07-04 12:34   ` [RFC] MAINTAINERS service, was: " Krzysztof Halasa
2008-07-04 13:44     ` Uwe Kleine-König
2008-07-04 14:08       ` Krzysztof Halasa
2008-07-07 13:19         ` Stefan Richter
2008-07-07 18:52           ` Krzysztof Halasa
2008-07-07 19:18             ` Stefan Richter
2008-07-07 22:37               ` Krzysztof Halasa [this message]
2008-07-07 23:33                 ` Stefan Richter
2008-07-09 20:14     ` Pavel Machek
2008-07-09 20:11   ` Pavel Machek
2008-07-04  8:50 ` Uwe Kleine-König

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=m37ibxl3r0.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --cc=Uwe.Kleine-Koenig@digi.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®