public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Gideon Glass <gid@cisco.com>
Cc: Richard Russon <ldm@flatcap.org>,
	"Eric S. Raymond" <esr@snark.thyrsus.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: esr cut off my genitives
Date: Sat, 1 Dec 2001 18:58:59 -0500	[thread overview]
Message-ID: <20011201185859.A14785@thyrsus.com> (raw)
In-Reply-To: <1007229787.2134.10.camel@addlestones> <Pine.GSO.4.33.0112011515550.23029-100000@andorra.cisco.com>
In-Reply-To: <Pine.GSO.4.33.0112011515550.23029-100000@andorra.cisco.com>; from gid@cisco.com on Sat, Dec 01, 2001 at 03:32:28PM -0800

Gideon Glass <gid@cisco.com>:
> "windows" is a plural noun, but "Windows" is a singular proper noun, and
> in "Windows LDM" it functions as an adjective.  Using possessive here is
> confusing because it suggests that this feature belongs to Windows, or
> that it's part of Windows itself, but obviously it isn't (the feature
> being referred to is part of Linux).  It is only *related* to Windows, so
> the adjectival "Windows" is the best thing to use.

That's correct.  Furthermore, those genitives were malformed. :-)

"Windows" is a singular noun.  Therefore the correct possessive form
is "Windows's", not "Windows'" -- the latter would be correct only 
if it were a *plural* noun.  

Similarly, the correct possessive form of "James" is not "James'" but
"James's".  This is often gotten wrong in these degenerate times,
mostly by the same people who confuse "its" with "it's". Etymologically,
"James's book" is a contraction of "James his book", which is how it
was done in Middle English (remembering the full form may help one
keep the rule straight).

> > Of course if it's a limitation of the new config tool I'll understand :-)
> > (and you'll need to apply the following, too).
> >
> > -IBM's S/390 architecture
> > +IBMs S/390 architecture
> 
> The "IBMs" plural construction is wrong since there is only one IBM.
> "IBMs" can't be possessive because there is no reason not to use an
> apostrophe to indicate possessive in this case.  Note that "IBM S/390
> architecture" could be used, with "IBM" (a noun) functioning as an
> adjective in the same manner as "Windows" above.  However, expressing the
> notion of ownership/control ("IBM's") conveys more information then mere
> association ("IBM"), so "IBM's" seems preferable here.

Also correct.  Ah, English-usage geeking.  Good clean fun for the 
whole family...
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

The real point of audits is to instill fear, not to extract revenue;
the IRS aims at winning through intimidation and (thereby) getting
maximum voluntary compliance
	-- Paul Strassel, former IRS Headquarters Agent Wall St. Journal 1980

  reply	other threads:[~2001-12-02  0:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01 17:14 Configure.help 2.5.1 update patch Eric S. Raymond
2001-12-01 18:03 ` esr cut off my genitives Richard Russon
2001-12-01 21:28   ` H. Peter Anvin
2001-12-01 23:32   ` Gideon Glass
2001-12-01 23:58     ` Eric S. Raymond [this message]
2001-12-03  1:01       ` Nicolas Pitre
2001-12-04  7:22         ` Aaron Lehmann

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=20011201185859.A14785@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=esr@snark.thyrsus.com \
    --cc=gid@cisco.com \
    --cc=ldm@flatcap.org \
    --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