| 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
| ||
|
Date: Fri, 1 Feb 2013 16:43:06 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-kernel@...r.kernel.org Cc: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> Subject: [PATCH] SubmittingPatches: add penalty for forcing a maintainer to edit a patch From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Maintainers have to hand-edit patches (body of patches and changelog entries) all the time. There needs to be some kind of penalty put into place to keep developers from abusing maintainers. Reported-by: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index c379a2a..d1bec01 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -93,7 +93,9 @@ includes updates for subsystem X. Please apply." The maintainer will thank you if you write your patch description in a form which can be easily pulled into Linux's source code management -system, git, as a "commit log". See #15, below. +system, git, as a "commit log". See #15, below. If the maintainer has +to hand-edit your patch, you owe them the beverage of their choice the +next time you see them. If your description starts to get long, that's a sign that you probably need to split up your patch. See #3, next. -- 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