supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "alice" <>
To: "Steve Litt" <>, <>
Subject: Re: [PATCH] Fix documentation typos
Date: Sat, 07 Jan 2023 10:01:25 +0100	[thread overview]
Message-ID: <CPLU3N674JTO.WE4319LFW19P@sumire> (raw)
In-Reply-To: <20230107033434.538134a1@mydesk.domain.cxm>

On Sat Jan 7, 2023 at 9:34 AM CET, Steve Litt wrote:
> Laurent Bercot said on Fri, 06 Jan 2023 11:58:55 +0000
> >>-file named <tt>S6_FDHOLDER_STORE_REGEX</tt> is found is the
> >><tt>env/</tt> +file named <tt>S6_FDHOLDER_STORE_REGEX</tt> is found
> >>in the <tt>env/</tt>  
> >
> >  Applied, thanks.
> >
> >
> >>-service readiness, you should give this option along with
> >><tt>up</tt>: the service is ready iff +service readiness, you should
> >>give this option along with <tt>up</tt>: the service is ready if  
> >
> >  Not a typo. "iff" means "if and only if", as any mathematician will
> >tell you. :)
> I'm not a mathematician, even though once upon a time I could do
> partial differential equations. I didn't know iff meant "if and only
> if". Just so everyone's on the same page, probably the easiest route to
> docs everyone understands is to replace iff with "if and only if".

as a passerby (and professional bike-shed designer), i would agree that is the
best solution. this isn't really a mathematical context, and it also has the
bonus of not looking like "domain-specific jargon" one can look up; an extra
letter merely looks like a typo to those that don't already know.

> SteveT
> Steve Litt 
> Autumn 2022 featured book: Thriving in Tough Times

      reply	other threads:[~2023-01-07  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2023-01-06 11:58 ` Laurent Bercot
2023-01-07  8:34   ` Steve Litt
2023-01-07  9:01     ` alice [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CPLU3N674JTO.WE4319LFW19P@sumire \ \ \ \

* 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).