public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: paulmck@linux.vnet.ibm.com
Cc: dhowells@redhat.com,
	Jaswinder Singh Rajput <jaswinder@kernel.org>,
	trivial <trivial@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 16/22] trivial: fix typo "that that" in multiple files
Date: Tue, 07 Jul 2009 18:17:57 +0100	[thread overview]
Message-ID: <19787.1246987077@redhat.com> (raw)
In-Reply-To: <20090707163336.GE6692@linux.vnet.ibm.com>


Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> The "that that" can read awkwardly even for native English (or, for that
> matter, American) speakers, even though it sounds quite natural in spoken
> English.

I think it sounds quite natural when you say it because you say them
differently - or at least I do.  The first 'that' is a conjunction, and the
second a determinative.  Possibly the determinative should be in italics, but
that's hard to do in plain text.

> Would it be possible to reword as for the RCU example?
> ...
> 	"likely that this process will submit another request soon, and that"

This is actually the as-iosched.txt example.

To use the RCU example:

	Therefore, as soon as a CPU is seen passing through any of these
	three states, we know that that CPU has exited any previous RCU
	read-side critical sections.

I think that in this example, "a CPU" should be paired with the "that"
determinative because you're not talking about the CPU you've got in your hand
per se, but a random CPU over there.

If you instead said "this CPU", being more specific, I think that's when you'd
use the "this" determinative:

	Therefore, as soon as this CPU is seen passing through any of these
	three states, we know that this CPU has exited any previous RCU
	read-side critical sections.

Of course, I'm not a qualified linguist - I know enough to make stuff up and
hopefully make it sound plausible.

David

  reply	other threads:[~2009-07-07 17:19 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 14:03 [GIT PULL] [PATCH 0/22] trivial fixes typo "foo foo" Jaswinder Singh Rajput
2009-07-07 14:05 ` [PATCH 1/22] trivial: fix typo "a a" in multiple files Jaswinder Singh Rajput
2009-07-07 14:06 ` [PATCH 2/22] trivial: fix typo "and and" " Jaswinder Singh Rajput
2009-07-07 14:08 ` [PATCH 3/22] trivial: fix typo "are are" " Jaswinder Singh Rajput
2009-07-07 14:09 ` [PATCH 4/22] trivial: fix typo "as as" " Jaswinder Singh Rajput
2009-07-07 14:10 ` [PATCH 5/22] trivial: fix typo "be be" " Jaswinder Singh Rajput
2009-07-07 14:11 ` [PATCH 6/22] trivial: fix typo "bit bit" " Jaswinder Singh Rajput
2009-07-07 14:12 ` [PATCH 7/22] trivial: fix typo "by by" " Jaswinder Singh Rajput
2009-07-07 14:13 ` [PATCH 8/22] trivial: fix typo "can can" Jaswinder Singh Rajput
2009-07-07 14:15 ` [PATCH 9/22] trivial: fix typo "could could" in multiple files Jaswinder Singh Rajput
2009-07-07 14:16 ` [PATCH 10/22] trivial: fix typo "from from" " Jaswinder Singh Rajput
2009-07-07 14:17 ` [PATCH 11/22] trivial: fix typo "has has" " Jaswinder Singh Rajput
2009-07-07 15:27   ` David Howells
2009-07-07 14:18 ` [PATCH 12/22] trivial: fix typo "lock lock" Jaswinder Singh Rajput
2009-07-07 14:19 ` [PATCH 13/22] trivial: fix typo "on on" in multiple files Jaswinder Singh Rajput
2009-07-07 15:29   ` David Howells
2009-07-07 14:20 ` [PATCH 14/22] trivial: fix typo "should should" " Jaswinder Singh Rajput
2009-07-07 14:21 ` [PATCH 15/22] trivial: fix typo "test test" Jaswinder Singh Rajput
2009-07-07 14:22 ` [PATCH 16/22] trivial: fix typo "that that" in multiple files Jaswinder Singh Rajput
2009-07-07 15:37   ` David Howells
2009-07-07 16:33     ` Paul E. McKenney
2009-07-07 17:17       ` David Howells [this message]
2009-07-07 16:30   ` Paul E. McKenney
2009-07-07 16:49     ` Jaswinder Singh Rajput
2009-07-07 14:23 ` [PATCH 17/22] trivial: fix typo "this this" " Jaswinder Singh Rajput
2009-07-07 14:24 ` [PATCH 18/22] trivial: fix typo "too too" Jaswinder Singh Rajput
2009-07-07 14:24 ` [PATCH 19/22] trivial: fix typo "was was" in multiple files Jaswinder Singh Rajput
2009-07-07 14:25 ` [PATCH 20/22] trivial: fix typo "we we" " Jaswinder Singh Rajput
2009-07-07 14:26 ` [PATCH 21/22] trivial: fix typo "with with" " Jaswinder Singh Rajput
2009-07-07 14:26 ` [PATCH 22/22] trivial: fix typo "you you" Jaswinder Singh Rajput
2009-07-07 15:44 ` [GIT PULL] [PATCH 0/22] trivial fixes typo "foo foo" David Howells
2009-07-07 16:11   ` Jesse Barnes
2009-07-07 22:15     ` Jiri Kosina
2009-07-08  4:18       ` Jaswinder Singh Rajput
2009-07-08  8:40       ` David Howells
2009-07-07 16:46   ` Jaswinder Singh Rajput
2009-07-07 16:30 ` [GIT PULL] V2 " Jaswinder Singh Rajput
2009-07-10  3:11   ` Jaswinder Singh Rajput
2009-07-10  8:42     ` Jiri Kosina
2009-07-10  8:49       ` Jaswinder Singh Rajput

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=19787.1246987077@redhat.com \
    --to=dhowells@redhat.com \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=trivial@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