public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Harry Wei <jiaweiwei.xiyou@gmail.com>
Cc: linux-kernel@vger.kernel.org, rdunlap@xenotime.net,
	linux-doc@vger.kernel.org, greg@kroah.com,
	randy.dunlap@oracle.com, akpm@linux-foundation.org
Subject: Re: [PATCH]Add Maintainer for MAINTAINERS file for us
Date: Mon, 09 May 2011 20:11:27 -0700	[thread overview]
Message-ID: <1304997087.19586.102.camel@Joe-Laptop> (raw)
In-Reply-To: <20110510025024.GA2575@gmail.com>

On Tue, 2011-05-10 at 10:50 +0800, Harry Wei wrote:
> I'd like to maintain this file for us. The patch is below.

Knock yourself out, but I think this won't
be too valuable.

I suggest you setup a git tree and create a
separate MAINTAINERS section entry and not use
the existing DOCUMENTATION section entry.

Part of handling MAINTAINERS is understanding
that any tree where you collect entries will
not be authoritative.  Lots of other MAINTAINERS
updates will occur outside of your tree and
nothing you do should hinder these updates.

One idea could be to separate all MAINTAINERS
sections into separate files in perhaps
a Maintainers directory.  You would not ever
have to alphabetize sections again.

Maybe add a little script to the Makefile to
aggregate them together as well.

Another would be to add a '*...' pattern type
to the files to match files in any directory
or add a new filename only pattern akin to
'find -name "pattern"' rather than specify both
the directory and file together.

Update scripts/get_maintainer.pl too if you
add some new file pattern types please.


  reply	other threads:[~2011-05-10  3:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  2:50 [PATCH]Add Maintainer for MAINTAINERS file for us Harry Wei
2011-05-10  3:11 ` Joe Perches [this message]
2011-05-10  4:51   ` Harry Wei
2011-05-10  5:15     ` Joe Perches
2011-05-10 10:17       ` Harry Wei

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=1304997087.19586.102.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=jiaweiwei.xiyou@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rdunlap@xenotime.net \
    /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