mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Krzysztof Halasa <khc@pm.waw.pl>
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: Mon, 07 Jul 2008 15:19:29 +0200	[thread overview]
Message-ID: <487217E1.2040205@s5r6.in-berlin.de> (raw)
In-Reply-To: <m37ic1zqqp.fsf@maximus.localdomain>

Krzysztof Halasa wrote:
> Uwe Kleine-König <Uwe.Kleine-Koenig@digi.com> writes:
> 
>> Why not make that a script that parses MAINTAINERS and lives in scripts/
>> and that can be used as --cc-cmd to git-send-email?  Then no service
>> needs to be maintained, you don't get the observers functionality
>> though.  (But that's what mailing lists are good for.)
>>
>> Of course MAINTAINERS needs to be modified to have the path specifiers.
> 
> Because then:
> - the action is not effective immediately but sometimes after few
>   months, not counting people still working with 2.6.12 or so.

We expect submissions to based on something more recent than 2.6.12.

Your patch service however...

> - IMHO adding Cc: patch-service is a bit easier than using a script
> - I think the "observers" thing is worth the effort. Now I only see
>   changes to certain areas I'm interested in when they are accepted
>   upstream.
> - maintaining the script is probably more work than maintaining the
>   database :-)
> 
> And with a service you can:
> - maintain a patch archive
> - be sure nobody tries to be "creative"
> - perhaps other things I haven't thought about.

...already exists.  Check the "L:" entries in MAINTAINERS.
-- 
Stefan Richter
-=====-==--- -=== --===
http://arcgraph.de/sr/

  reply	other threads:[~2008-07-07 13:19 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 [this message]
2008-07-07 18:52           ` Krzysztof Halasa
2008-07-07 19:18             ` Stefan Richter
2008-07-07 22:37               ` Krzysztof Halasa
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=487217E1.2040205@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=Uwe.Kleine-Koenig@digi.com \
    --cc=dwmw2@infradead.org \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.org \
    /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®