public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <Uwe.Kleine-Koenig@digi.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: 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: Fri, 4 Jul 2008 15:44:26 +0200	[thread overview]
Message-ID: <20080704134426.GA32700@digi.com> (raw)
In-Reply-To: <m3k5g1zv3u.fsf_-_@maximus.localdomain>

Hello,

Krzysztof Halasa wrote:
> Oliver Neukum <oliver@neukum.org> writes:
> 
> >> I wanted to add an entry to MAINTAINERS and while doing it I saw that in
> >> the corresponding region the alphabetic ordering is broken.  Then I
> >> inteded to fix that up for a trivial patch.  Next was to check the rest
> >> of the file and there are so much misorderings that it's not sensible to
> >> choose the trivial path anymore as there are currently 114 entries out
> >> of order[1].
> >
> > What good does alphabetic ordering? You'll grep it anyway.
> 
> I was thinking about a mailing list / database service instead:
> - source file/directory-based (e.g. someone could maintain whole
>   drivers/, someone else drivers/char and others drivers/char/asdfg.[ch])
> - people would be able to add themselves as "observers" using mail
>   and/or HTML interface
> - sending a patch would automatically trigger Cc: to all people
>   registered as maintainers (or "observers") for the files modified
> - full recipient list would be present in mail sent by the service, so
>   the following discussion wouldn't need it anymore. It would be used
>   only for posting patches.
> - as such, I don't expect a need for spam filtering - messages
>   containing no patch would be rejected in the SMTP session.
> 
> Pro: no more missing Cc:, no more manual lookups and guessing, you
>      just Cc: the service, possibility for "observers".
> Con: another thing to create and maintain, you don't immediately know
>      who exactly has been sent a copy.
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.

Best regards
Uwe

-- 
Uwe Kleine-König, Software Engineer
Digi International GmbH Branch Breisach, Küferstrasse 8, 79206 Breisach, Germany
Tax: 315/5781/0242 / VAT: DE153662976 / Reg. Amtsgericht Dortmund HRB 13962

  reply	other threads:[~2008-07-04 13:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04  6:34 alphabetic ordering of MAINTAINERS 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 [this message]
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
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=20080704134426.GA32700@digi.com \
    --to=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