public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "Uwe Kleine-König" <ukleinek@strlen.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Ben Dooks <ben-linux@fluff.org>,
	Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] List of maintainers (draft #3)
Date: Mon, 22 Sep 2008 22:10:33 -0700	[thread overview]
Message-ID: <1222146633.18133.51.camel@localhost> (raw)
In-Reply-To: <20080922194242.GA792@strlen.de>

On Mon, 2008-09-22 at 21:42 +0200, Uwe Kleine-König wrote:
> Continuing planning how to implement such an automation I found that
> git-send-email already has an option --cc-cmd=/path/to/some/program

I added cc-cmd to git-send-email.

> To go forward with how to specify a file <-> maintainer relation I
> suggest to standardize a field F in MAINTAINERS that specifies the
> associated files.

I did roughly the same thing last year with MAINTAINERS entries
and a script for patch submission.

http://lkml.org/lkml/2007/8/13/17

There were a few iterations before Linus said he didn't much
like the idea.

http://lkml.org/lkml/2007/8/13/1139

I still think it's useful and don't think a particularly
better way exists to generate this information.

I think the best way to manage this content is to separate
the monolithic MAINTAINERS into separate Maintainers/subsection
files (which would be automatically alphabetized) and to create
an aggregated MAINTAINERS file via Makefile.

If per directory .maintainers files are created, there'll
be roughly the same number of files.

http://lkml.org/lkml/2007/8/17/119

cheers, Joe


  reply	other threads:[~2008-09-23  5:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07 14:54 [RFC] List of maintainers (draft #3) Denis Vlasenko
2008-09-22  8:12 ` Uwe Kleine-König
2008-09-22  9:12   ` Ben Dooks
2008-09-22  9:23     ` Pekka Enberg
2008-09-22 16:40       ` H. Peter Anvin
2008-09-22 19:42         ` Uwe Kleine-König
2008-09-23  5:10           ` Joe Perches [this message]
2008-09-29 17:56         ` Pavel Machek
2008-10-01  0:10           ` Randy Dunlap
2008-10-01  0:09             ` Joe Perches
2008-10-01  0:35               ` Randy Dunlap
2008-10-01 13:36                 ` Pavel Machek
2008-10-01 15:41                   ` Randy Dunlap
2008-10-01 12:25           ` [PATCH] [RFC] Add a script that searched per-file maintainers for a patch 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=1222146633.18133.51.camel@localhost \
    --to=joe@perches.com \
    --cc=ben-linux@fluff.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=ukleinek@strlen.de \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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