lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1304997087.19586.102.camel@Joe-Laptop>
Date:	Mon, 09 May 2011 20:11:27 -0700
From:	Joe Perches <joe@...ches.com>
To:	Harry Wei <jiaweiwei.xiyou@...il.com>
Cc:	linux-kernel@...r.kernel.org, rdunlap@...otime.net,
	linux-doc@...r.kernel.org, greg@...ah.com, randy.dunlap@...cle.com,
	akpm@...ux-foundation.org
Subject: Re: [PATCH]Add Maintainer for MAINTAINERS file for us

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ