From: Joe Lawrence <joe.lawrence@redhat.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: Matthew Wilcox <willy@infradead.org>,
attreyee-muk <tintinm2017@gmail.com>,
jpoimboe@kernel.org, jikos@kernel.org, pmladek@suse.com,
corbet@lwn.net, live-patching@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] Took care of some grammatical mistakes
Date: Wed, 29 Nov 2023 09:48:07 -0500 [thread overview]
Message-ID: <1f66c647-e51b-4640-cbff-67b17e2077ad@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.21.2311291105430.12159@pobox.suse.cz>
On 11/29/23 05:08, Miroslav Benes wrote:
>
> I am not a native speaker, but "step on each other's toe" sounds the best
> to me. Or perhaps even "they need to be aware of each other and not step
> on their toes" since it is then kind of implied? English is difficult :).
>
Native speaker here, so don't ask me what's grammatically accurate :D I
would definitely say "step on" vs. "step over". I would also write
"each other's toes", but not flinch if I read "each others' toes" or
even "each others toes".
After thinking about it for more that 30s, I might consider rewording
the sentence to avoid the idiom altogether, something like: "Therefore
they need to coordinate to avoid interfering with each other."
--
Joe
prev parent reply other threads:[~2023-11-29 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 15:57 attreyee-muk
2023-11-27 16:47 ` Jonathan Corbet
2023-11-27 19:41 ` Randy Dunlap
2023-11-28 14:12 ` Matthew Wilcox
2023-11-28 16:18 ` Randy Dunlap
2023-11-29 10:08 ` Miroslav Benes
2023-11-29 12:47 ` Bagas Sanjaya
2023-11-29 14:48 ` Joe Lawrence [this message]
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=1f66c647-e51b-4640-cbff-67b17e2077ad@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=corbet@lwn.net \
--cc=jikos@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=tintinm2017@gmail.com \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®