From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, randy.dunlap@oracle.com,
akpm@linux-foundation.org, greg@kroah.com,
linux-doc@vger.kernel.org
Subject: Re: [PATCH]Add Maintainer for MAINTAINERS file for us
Date: Tue, 10 May 2011 12:51:45 +0800 [thread overview]
Message-ID: <20110510045142.GA2888@gmail.com> (raw)
In-Reply-To: <1304997087.19586.102.camel@Joe-Laptop>
On Mon, May 09, 2011 at 08:11:27PM -0700, Joe Perches wrote:
> 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.
The patch has been updatated below.
>
> 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.
This may a little complex. Keeping just MAINTAINERS file
with alphabetical order is well for us.
I will also write a shell script for MAINTAINERS, which
can not only check whether it is in alphabetical order
but may also take orders for us.
The script is been programing by me and my friend.
When it is okay, i will patch for kernel.
>
> 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.
Signed-off-by: Harry Wei <harryxiyou@gmail.com>
---
MAINTAINERS | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index af39897..629dd7c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4043,6 +4043,12 @@ S: Maintained
F: drivers/net/macvlan.c
F: include/linux/if_macvlan.h
+MAINTAINERS-FILE
+M: Harry Wei <harryxiyou@gmail.com>
+L: linux-doc@vger.kernel.org
+S: Maintained
+F: MAINTAINERS
+
MAN-PAGES: MANUAL PAGES FOR LINUX -- Sections 2, 3, 4, 5, and 7
M: Michael Kerrisk <mtk.manpages@gmail.com>
W: http://www.kernel.org/doc/man-pages
--
1.7.0.4
next prev parent reply other threads:[~2011-05-10 4:52 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
2011-05-10 4:51 ` Harry Wei [this message]
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=20110510045142.GA2888@gmail.com \
--to=jiaweiwei.xiyou@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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