From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Patch Question
Date: Wed, 19 Apr 2017 18:13:34 +0200 [thread overview]
Message-ID: <20170419161334.GA32742@kroah.com> (raw)
In-Reply-To: <CAO62RXdj24OPnNzXraDsrp+zw9PnwaBY5wJ+2CYmBix+WzZK_w@mail.gmail.com>
On Wed, Apr 19, 2017 at 09:54:33AM -0600, Perry Hooker wrote:
> At this point, no one has commented on the accuracy of my analysis.
> Such comments are exactly what I'm hoping for (and what I requested -
> not "demanded" - in my replies).
As the one responsible for actually applying this specific patch, I find
this pretty "interesting"...
It's _your_ responsibility to convince me that your patch is correct and
should be applied. If no one respondes after a week or so, resend it,
with your additional information in the changelog so that the same
conversation doesn't happen again.
Patches get dropped all the time, remember, I get _hundreds_ of them
every day. If I see a disagreement on a patch, then it goes to the end
of the line, or usually just deleted from my queue. I rely on the fact
that it's up to the submitter to resend and handle the discussion.
Yes, we waste engineering time and effort by doing this, and that's
fine, we have thousands of developers, but very few maintainers. It's
their time that is valuable and the process is optimized for.
good luck!
greg k-h
next prev parent reply other threads:[~2017-04-19 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 23:28 Patch Question Perry Hooker
2017-04-17 23:48 ` Mandeep Sandhu
2017-04-17 23:58 ` Tobin C. Harding
2017-04-18 23:07 ` Perry Hooker
2017-04-19 0:11 ` Tobin C. Harding
2017-04-19 15:54 ` Perry Hooker
2017-04-19 16:13 ` Greg KH [this message]
2017-04-19 16:46 ` Perry Hooker
2017-04-19 20:48 ` Lino Sanfilippo
2017-04-19 13:27 ` Lino Sanfilippo
2017-04-19 15:41 ` Perry Hooker
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=20170419161334.GA32742@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).