mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Ben Dooks" <ben-linux@fluff.org>
Cc: "Uwe Kleine-K?nig" <ukleinek@strlen.de>,
	"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 12:23:25 +0300	[thread overview]
Message-ID: <84144f020809220223jbb71877ued9d3b2569c4cd67@mail.gmail.com> (raw)
In-Reply-To: <20080922091256.GH1916@fluff.org.uk>

Hi,

On Mon, Sep 22, 2008 at 12:12 PM, Ben Dooks <ben-linux@fluff.org> wrote:
> I was thinking of at least making MAINTAINERS per-subsystem, it is a
> large file and would be easier for the people submitting patcehs to
> avoid having to touch a common file.

Figuring out whom to send a patch to is not something you can automate
because it not only depends on what you're changing but *how* you're
changing it. The classic case being that whenever you change something
related to RCU that's non-trivial, you almost certainly want to CC
Paul "RCU" McKenney. But there's no *file* or *directory* pattern that
can automatically tell you this.

Furthermore, if you're hacking on a specific part of the kernel, you
almost certainly are doing it wrong if you don't know who the relevant
maintainers are. For simple janitorial patches, you probably should
just work out the *top-level* maintainers (davem for networking, ingo
et al for x86, and so on) and send the patches to them. And when these
simple rules fail you, fall back to patch bombing Andrew.

                             Pekka

  reply	other threads:[~2008-09-22  9:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07 14:54 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 [this message]
2008-09-22 16:40       ` H. Peter Anvin
2008-09-22 19:42         ` Uwe Kleine-König
2008-09-23  5:10           ` Joe Perches
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=84144f020809220223jbb71877ued9d3b2569c4cd67@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=ben-linux@fluff.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®