From: William Allen Simpson <william.allen.simpson@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: huananhu@huawei.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 17/11]Optimize the upload speed for PPP connection.
Date: Wed, 18 Nov 2009 00:04:47 -0500 [thread overview]
Message-ID: <4B03806F.7010803@gmail.com> (raw)
In-Reply-To: <20091117.034959.159359822.davem@davemloft.net>
David Miller wrote:
> From: William Allen Simpson <william.allen.simpson@gmail.com>
> Date: Tue, 17 Nov 2009 05:20:09 -0500
>
>> What David may have meant, had he followed
>> Documentation/ManagementStyle or had any project management skills
>> what-so-ever, is that you need to follow
>> Documentation/SubmittingPatches more carefully.
>
> Are personal attacks on me really necessary?
>
Actually, ironic sarcasm (juxtaposition) is a form of humor, fairly
popular on such venues as "The Daily Show". :-)
> Do you want me to look closely at your patches with a high priority
> when you submit them for inclusion?
>
Great, you're planning to start a new practice? So far, I've only been
blessed with:
* 1st contact (Oct 2):
"Otherwise asking for a is absolutely pointless as we have no
context in which to judge the code you're showing us."
The context (and entire previous patch) was pointed at by a link
in the message, and an internet-draft, but that would have required
effort (clicking and browsing).
Not exactly what I'd call "look closely at your patches"....
* 2nd contact (Oct 5), replying to my post of Oct 3:
"struct tcp_sock is already WAY TOO BIG on 64-bit systems, adding
20 more bytes to it for some odd-ball feature is not something I'm
willing to do, sorry."
Always delighted to know our work is an "odd-ball feature"....
* 3rd contact, sending private email to you as maintainer, suggested by
Andi Kleen's "On submitting kernel patches" for resolving conflicts,
and getting flamed for sending private email to you!
* Recently, flamed for re-sending a query (after waiting 30 days):
"Complaining that your work isn't getting looked at in a timely
manner will always have the exact opposite effect that you want,
it makes people have a smaller desire to look at your stuff."
Yeah, 30 days just isn't long enough.... Fortunately, Eric Dumazet
and Paul E. McKenney were really helpful (and others privately), and
I thank them again!
* 2 days ago, flamed again for re-sending a patch (after waiting 5 days),
although you'd never Ack'd or otherwise responded.
> You may be right, but that doesn't matter if you're interested in
> working together with me in the future. There are diplomatic ways to
> do everything, and this wasn't one of those ways.
>
Working *together* would be handy! But that implies cooperation and
respect -- *not* biting the newbies nor dropping the F-bomb.
next prev parent reply other threads:[~2009-11-18 5:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 9:19 [PATCH 17/11]Optimize the upload speed for PPP connection fangxiaozhi 00110321
2009-11-17 9:22 ` David Miller
2009-11-17 10:20 ` William Allen Simpson
2009-11-17 11:14 ` Jarek Poplawski
2009-11-17 11:49 ` William Allen Simpson
2009-11-17 11:54 ` Franko Fang
2009-11-17 11:49 ` David Miller
2009-11-18 5:04 ` William Allen Simpson [this message]
2009-11-18 7:51 ` Jarek Poplawski
2009-11-21 9:29 ` Pavel Machek
2009-11-21 12:21 ` Jarek Poplawski
2009-11-21 19:00 ` David Miller
2009-11-17 17:37 ` Alexander Clouter
2009-11-17 18:49 ` Valdis.Kletnieks
2009-11-18 4:00 ` William Allen Simpson
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=4B03806F.7010803@gmail.com \
--to=william.allen.simpson@gmail.com \
--cc=davem@davemloft.net \
--cc=huananhu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 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).