From: Linus Torvalds <torvalds@transmeta.com>
To: Michael Hayes <mike@aiinc.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix breakage caused by spelling 'fix'
Date: Thu, 6 Mar 2003 13:57:10 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0303061356030.8521-100000@home.transmeta.com> (raw)
In-Reply-To: <200303062141.h26LfZK19533@aiinc.aiinc.ca>
On Thu, 6 Mar 2003, Michael Hayes wrote:
>
> This fixes a spelling "fix" that resulted in a compile error.
>
> With apologies to Russell King.
Ugh, please make things like this just write out the full non-contracted
thing. Ie "cannot" is a perfectly fine word, we don't need to force
spelling errors.
Linus
next prev parent reply other threads:[~2003-03-06 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 21:41 [PATCH] Fix breakage caused by spelling 'fix' Michael Hayes
2003-03-06 21:57 ` Linus Torvalds [this message]
2003-03-06 22:37 ` Steven Cole
2003-03-06 21:59 ` Marc-Christian Petersen
2003-03-06 22:28 ` John Bradford
2003-03-06 22:48 ` Tomas Szepe
2003-03-06 22:27 ` Russell King
2003-03-06 22:09 Michael Hayes
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=Pine.LNX.4.44.0303061356030.8521-100000@home.transmeta.com \
--to=torvalds@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@aiinc.ca \
/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).