linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Matthew Wilcox <willy@infradead.org>
Cc: Cai Huoqing <caihuoqing@baidu.com>,
	tj@kernel.org, lizefan.x@bytedance.com, hannes@cmpxchg.org,
	cgroups@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] cgroup: Fix typo in comments and documents
Date: Fri, 30 Jul 2021 13:16:46 -0600	[thread overview]
Message-ID: <87im0ra9y9.fsf@meer.lwn.net> (raw)
In-Reply-To: <YQQUwX+/1N9utKEN@casper.infradead.org>

Matthew Wilcox <willy@infradead.org> writes:

> On Fri, Jul 30, 2021 at 08:51:29AM -0600, Jonathan Corbet wrote:
>> Cai Huoqing <caihuoqing@baidu.com> writes:
>> 
>> > Fix typo: iff  ==> if
>> >
>> > Signed-off-by: Cai Huoqing <caihuoqing@baidu.com>
>> 
>> This is becoming an FAQ ...  "iff" in mathematical English means "if and
>> only if"; its usage in these documents is correct.
>
> ... and yet it's clearly not understood.  Similarly to the [start..end)
> convention (also the [start..end[ convention).  Should we deprecate
> use of it in kernel documentation, and if so, what should we replace it
> with?

I'm never quite sure what to do with these things...we want to be
inclusive, but we don't want to hobble the language we use beyond a
certain point.  We could ask people to spell out "if and only if", I
suppose, but that sounds like the kind of thing that leads to unpleasant
messages in my inbox.

Thanks,

jon

  reply	other threads:[~2021-07-30 19:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  5:16 [PATCH] cgroup: Fix typo in comments and documents Cai Huoqing
2021-07-30 13:43 ` Hu Haowen
2021-07-30 13:44 ` Hu Haowen
2021-07-30 14:53   ` Shakeel Butt
2021-07-30 14:54     ` Cai,Huoqing
2021-07-30 16:07       ` Hu Haowen
2021-07-30 14:51 ` Jonathan Corbet
2021-07-30 15:03   ` Matthew Wilcox
2021-07-30 19:16     ` Jonathan Corbet [this message]
2021-08-01  3:39     ` Hu Haowen

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=87im0ra9y9.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=caihuoqing@baidu.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=tj@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).