From: Tomas Szepe <szepe@pinerecords.com>
To: John Bradford <john@grabjohn.com>
Cc: Marc-Christian Petersen <m.c.p@wolk-project.de>,
mike@aiinc.ca, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: re: [PATCH] Fix breakage caused by spelling 'fix'
Date: Thu, 6 Mar 2003 23:48:12 +0100 [thread overview]
Message-ID: <20030306224812.GB14525@louise.pinerecords.com> (raw)
In-Reply-To: <200303062228.h26MSYYj000170@81-2-122-30.bradfords.org.uk>
> [john@grabjohn.com]
>
> > > This fixes a spelling "fix" that resulted in a compile error.
> > > With apologies to Russell King.
> > > diff -ur a/include/asm-arm/proc-fns.h b/include/asm-arm/proc-fns.h
> > > --- a/include/asm-arm/proc-fns.h Tue Mar 4 19:29:20 2003
> > > +++ b/include/asm-arm/proc-fns.h Thu Mar 6 11:46:15 2003
> > > @@ -125,7 +125,7 @@
> > >
> > > #if 0
> > > * The following is to fool mkdep into generating the correct
> > > - * dependencies. Without this, it can't figure out that this
> > > + * dependencies. Without this, it cant figure out that this
> > A spelling fix should be a right spelling fix ;)
> >
> > So either "cannot" or "can not" but not "cant" :)
>
> "Can not" is technically wrong.
While "can not" is not necessarily bad English, it's uncommon
and should probably be avoided, because its use might produce
sentences ambivalent in meaning.
<quote>
Can/could: modal auxiliary verbs --
...
h/ contracted negative forms are "can't" and "couldn't."
Cannot is usually written as one word.
</quote>
Swan, Michael: Practical English Usage
Oxford University Press, Second Edition, 1995
p. 104, item 122
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-03-06 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 21:41 Michael Hayes
2003-03-06 21:57 ` Linus Torvalds
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 [this message]
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=20030306224812.GB14525@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=mike@aiinc.ca \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®