From: "Tom Schwindl" <schwindl@posteo.de>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: <alx@kernel.org>, <alx.manpages@gmail.com>, <linux-man@vger.kernel.org>
Subject: Re: [PATCH] CONTRIBUTING: tfix
Date: Sat, 11 Mar 2023 14:17:35 +0000 [thread overview]
Message-ID: <CR3MA1O55PTL.Z871EDUY4TFS@morphine> (raw)
In-Reply-To: <20230309152857.usupq3b4ekjhi7pv@illithid>
Hi Branden,
On Thu Mar 9, 2023 at 4:28 PM CET, G. Branden Robinson wrote:
> [natural language grammar]
>
> Hi Tom,
>
> At 2023-03-09T07:39:00+0000, Tom Schwindl wrote:
> > as I'm not a native speaker, I wonder if the "be" is correct in this
> > context. I haven't changed it for now because it's likely that it's
> > just me who thinks that this sounds awkward.
> [...]
> > Please CC any relevant developers and mailing lists that may
> > know about or be interested in the discussion.
>
> In this respect, English is subject to mechanical analysis to resolve
> the issue. You will observe the presence of a coordinating conjunction
> ("and" or "or"; there are others but these are by far the most common).
> You can decide the grammar of the sentence by eliminating one of the
> branches of the conjunction.
>
> ...that (may (know about) or (be interested in) the discussion).
>
> Possibly one of the sources of confusion here is that the conjunction is
> applied after the modal auxiliary verb "may".
>
> While that's not non-standard,[1] it does reveal that a recast to more
> clearly apply the coordinating conjunction after the _sub_ordinating
> conjunction "that", as follows.
>
> ...that (may know about) or (may be interested in) the discussion.
>
> The fact that I need fewer pairs of parentheses to suggest the
> recommended parse might indeed recommend it over the former alternative.
>
> Do not underestimate the power of conjunction elimination; I frequently
> use this tool to decide grammatical questions in my own writing.[2] I
> cannot think of a time that it has led me to an incorrect construction.
>
> Lest anyone feel badly, I note that native English speakers often screw
> up much simpler applications of coordinating conjunctions than this.
>
> *Jackie and me are going to the beach.
> *This discussion is to be kept between you and I.
>
> Both are wrong, wrong, wrong, but you run into them all the time even in
> attempts at formal writing (particularly the latter--people get anxious,
> it seems, and think that this error somehow puts their text into a
> higher register).
>
> Regards,
> Branden
>
> [1] Example: "The market is full of things that you might need or want."
> [2] which can get highfalutin' and florid, to say nothing of loquacious
Thanks for the thorough explanation! I really appreciate it.
--
Best Regards,
Tom Schwindl
next prev parent reply other threads:[~2023-03-11 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 7:39 [PATCH] CONTRIBUTING: tfix Tom Schwindl
2023-03-09 13:07 ` Alejandro Colomar
2023-03-09 15:28 ` G. Branden Robinson
2023-03-11 14:17 ` Tom Schwindl [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-18 9:17 Thomas Voss
2022-11-18 11:24 ` Alejandro Colomar
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=CR3MA1O55PTL.Z871EDUY4TFS@morphine \
--to=schwindl@posteo.de \
--cc=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@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