From: Randy Dunlap <rdunlap@xenotime.net>
To: Valdis.Kletnieks@vt.edu
Cc: David Newall <davidn@davidnewall.com>,
Daolong Wang <ahlongxp@gmail.com>,
David Miller <davem@davemloft.net>,
bhutchings@solarflare.com, lizf@cn.fujitsu.com,
qhfeng.kernel@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NET: fix wrong English expression in comments
Date: Tue, 13 Jan 2009 15:30:31 -0800 [thread overview]
Message-ID: <496D2417.4030705@xenotime.net> (raw)
In-Reply-To: <25981.1231888978@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Tue, 13 Jan 2009 19:11:19 +1030, David Newall said:
>> Daolong Wang wrote:
>>> The patch will make sense for some people. I was puzzled about the
>>> double-negative for quite a while.
>>>
>> "Don't add nothing," is not a colloquialism; it's just bad grammar. The
>> meaning is that you must not add no thing, therefore that you must add
>> something. It is a common error amongst English speakers, even amongst
>> those who speak good, but. :-)
>
> Those of us who have worked with weakly-typed languages who have coded
> stuff like 'X + 0.0' to cast X from string to floating point know all
> too well that sometimes, adding nothing is in fact what you want to do.
That didn't sway the argument^W discussion IMO.
for the patch: Acked-by: Randy Dunlap <rdunlap@xenotime.net> // :)
~Randy
next prev parent reply other threads:[~2009-01-13 23:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 18:36 [PATCH] NET: fix wrong English expression in comments Qinghuang Feng
2009-01-12 1:05 ` Li Zefan
2009-01-12 1:39 ` Ben Hutchings
2009-01-13 5:53 ` David Miller
2009-01-13 6:16 ` Daolong Wang
2009-01-13 8:41 ` David Newall
2009-01-13 9:04 ` Alan Cox
2009-01-13 12:09 ` David Newall
2009-01-13 23:22 ` Valdis.Kletnieks
2009-01-13 23:30 ` Randy Dunlap [this message]
[not found] ` <6b1ba94c0901122336r511fa316o5f520a8d2d9d6e0@mail.gmail.com>
2009-01-13 7:44 ` David Miller
2009-01-13 7:56 ` Li Zefan
2009-01-13 7:57 ` Eric Dumazet
2009-01-13 8:52 ` Oliver Hartkopp
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=496D2417.4030705@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=ahlongxp@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=davidn@davidnewall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=qhfeng.kernel@gmail.com \
/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).