From: Val Henson <val@nmt.edu>
To: Steven Cole <elenstev@mesatop.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Those ruddy punctuation fixes
Date: Thu, 6 Mar 2003 18:04:22 -0700 [thread overview]
Message-ID: <20030307010422.GI26725@boardwalk> (raw)
In-Reply-To: <1046920285.3786.68.camel@spc1.mesatop.com>
On Wed, Mar 05, 2003 at 08:11:11PM -0700, Steven Cole wrote:
>
> That is why I was very careful with my its -> it's patch.
> In the two files where an extra apostrophe would have broken
> the build, I changed its to it is. Why not just leave it alone?
> Because some well-meaning spelling fixer may come along in the
> future and break it, just like in proc-fns.h.
Wait, this sounds like a conversation with the Mafia:
"Pay us protection money."
"Why do we need to pay you for protection?"
"So we can protect you from criminals like ourselves."
I'd rather solve this problem by making standalone spelling fixes and
other cosmetic changes taboo. Cosmetic changes combined with actual
useful code changes are fine with me. If you're risking breaking the
build, there should be some benefit that justifies the risk.
Consider this a vote against standalone spelling/typo patches.
-VAL (normally a total pedant about spelling and grammar)
next prev parent reply other threads:[~2003-03-07 0:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 11:10 Those ruddy punctuation fixes Russell King
2003-03-05 11:22 ` John Bradford
2003-03-05 14:18 ` Mike Dresser
2003-03-06 1:50 ` jw schultz
2003-03-06 9:58 ` Russell King
2003-03-06 10:46 ` John Bradford
2003-03-05 12:20 ` Dave Jones
2003-03-05 11:37 ` good info on memory management Prasad Kamath
2003-03-05 12:03 ` Terje Eggestad
2003-03-06 8:16 ` Ranjeet Shetye
2003-03-06 3:11 ` Those ruddy punctuation fixes Steven Cole
2003-03-07 1:04 ` Val Henson [this message]
2003-03-07 2:44 ` Steven Cole
2003-03-07 3:33 ` Martin J. Bligh
2003-03-07 4:02 ` Steven Cole
2003-03-07 5:11 ` Martin J. Bligh
2003-03-07 17:04 ` Hans Reiser
[not found] ` <mailman.1047000901.5238.linux-kernel2news@redhat.com>
2003-03-07 3:07 ` Pete Zaitcev
-- strict thread matches above, loose matches on Subject: below --
2003-03-07 7:16 Dan Kegel
2003-03-07 17:17 ` Benjamin LaHaise
2003-03-07 18:00 ` Dan Kegel
2003-03-07 23:15 ` Alan Cox
2003-03-08 0:52 ` Dave Jones
2003-03-08 0:04 ` Randy.Dunlap
2003-03-08 0:29 ` Werner Almesberger
2003-03-08 1:09 ` Dan Kegel
2003-03-08 2:18 ` Werner Almesberger
2003-03-08 1:08 ` Alan Cox
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=20030307010422.GI26725@boardwalk \
--to=val@nmt.edu \
--cc=davej@codemonkey.org.uk \
--cc=elenstev@mesatop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox