From: Randy Dunlap <rdunlap@infradead.org>
To: Anca Emanuel <anca.emanuel@gmail.com>
Cc: Joe Perches <joe@perches.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH] SubmittingPatches: add penalty for forcing a maintainer to edit a patch
Date: Fri, 01 Feb 2013 14:10:45 -0800 [thread overview]
Message-ID: <510C3D65.6010200@infradead.org> (raw)
In-Reply-To: <CAJL_dMuMnq0=4vv0GriQqUhwnR=gwcnok3rXTsanVYZ5cdLfkQ@mail.gmail.com>
On 02/01/13 13:07, Anca Emanuel wrote:
> Joe, read lkml and decide after that.
> I fully apove the pathch.
>
> Reviewed-by: Anca Emanuel <anca.emanuel@gmail.com>
>
> Review-requested-by: Joe Perches <joe@perches.com>
>
>
> Comments:
> You have 3 kernels to maintain as stable, plus drivers, plus etc.
> If somebody post something without reading the docs, and you have to
> repeat to them the same, again and more, then you MUST give an beer.
If someone is a repeat-repeat offender, they should just learn
how to submit patches correctly. I.e., the maintainer should just
keep saying to them, Sorry, please submit your patch correctly
so that I can apply it.
> On Fri, Feb 1, 2013 at 5:48 PM, Joe Perches <joe@perches.com> wrote:
>> On Fri, 2013-02-01 at 16:43 +0100, Greg Kroah-Hartman wrote:
>>> 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.
>>
>> No, there doesn't.
>>
>> It's funny as a joke, it's not as an actual patch.
--
~Randy
next prev parent reply other threads:[~2013-02-01 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 15:43 [PATCH] SubmittingPatches: add penalty for forcing a maintainer to edit a patch Greg Kroah-Hartman
2013-02-01 15:48 ` Joe Perches
2013-02-01 21:07 ` Anca Emanuel
2013-02-01 22:10 ` Randy Dunlap [this message]
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=510C3D65.6010200@infradead.org \
--to=rdunlap@infradead.org \
--cc=anca.emanuel@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--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.