linux-kernel - Re: [PATCH 2/2] MAINTAINERS

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: <20070818100505.6a3cd83a.randy.dunlap@oracle.com>
Date:	Sat, 18 Aug 2007 10:05:05 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Joe Perches <joe@...ches.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] MAINTAINERS

On Sat, 18 Aug 2007 00:08:54 -0700 Joe Perches wrote:

> Added patterns to describe files maintained.
> 
> Signed-off-by: Joe Perches <joe@...ches.com>
> 
> 
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d3a0684..d7fe1c5 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -19,40 +19,44 @@ trivial patch so apply some common sense.
>  3.	Make sure your changes compile correctly in multiple
>  	configurations. In particular check that changes work both as a
>  	module and built into the kernel.
>  
>  4.	When you are happy with a change make it generally available for
>  	testing and await feedback.
>  
>  5.	Make a patch available to the relevant maintainer in the list. Use
>  	'diff -u' to make the patch easy to merge. Be prepared to get your
>  	changes sent back with seemingly silly requests about formatting
>  	and variable names.  These aren't as silly as they seem. One
>  	job the maintainers (and especially Linus) do is to keep things
>  	looking the same. Sometimes this means that the clever hack in
>  	your driver to get around a problem actually needs to become a
>  	generalized kernel feature ready for next time.
>  
>  	PLEASE check your patch with the automated style checker
>  	(scripts/checkpatch.pl) to catch trival style violations.
>  	See Documentation/CodingStyle for guidance here.
>  
> +	PLEASE include the appropriate maintainers and developers
> +	that have modified files touched by your patch by using the

s/that/who/

> +	automated CC generator (scripts/get_maintainer.pl)


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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/