From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: [PATCH] SubmittingPatches: add penalty for forcing a maintainer to edit a patch
Date: Fri, 1 Feb 2013 16:43:06 +0100 [thread overview]
Message-ID: <20130201154306.GA28473@kroah.com> (raw)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.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@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.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.
next reply other threads:[~2013-02-01 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 15:43 Greg Kroah-Hartman [this message]
2013-02-01 15:48 ` [PATCH] SubmittingPatches: add penalty for forcing a maintainer to edit a patch Joe Perches
2013-02-01 21:07 ` Anca Emanuel
2013-02-01 22:10 ` Randy Dunlap
2013-02-02 10:26 ` Andrew Morton
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=20130201154306.GA28473@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.