From: "Štěpán Němec" <stepnem@smrk.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 5/5] Fix some typos/grammar/errors in docs and comments
Date: Mon, 28 Aug 2023 23:22:47 +0200 [thread overview]
Message-ID: <20230828232247+0200.172961-stepnem@smrk.net> (raw)
In-Reply-To: <20230828211154.M621959@dcvr>
On Mon, 28 Aug 2023 21:11:54 +0000
Eric Wong wrote:
> Perhaps something like the following is clearer?
>
> -Well-known TCP ports automatically get TLS or STARTTLS support
> -If using systemd-compatible socket activation and a TCP listener
> -on port well-known ports (563 is inherited, it is automatically
> -NNTPS when this option is given. When a listener on port 119 is
> -inherited and this option is given, it automatically gets
> -STARTTLS support.
> +Well-known TCP ports automatically get TLS or STARTTLS support if using
> +systemd-compatible socket activation. That is, ports 443, 563, 993, and
> +995 support HTTPS, NNTPS, IMAPS, and POP3S, respectively; while ports
> +110, 119, and 143 support STARTTLS on POP3, NNTP, and IMAP,
> +respectively.
Crystal clear, thank you! Maybe add "With this option, [well-known...]"
at the beginning, to avoid any possible confusion (it should go without
saying, but being explicit doesn't hurt (and the original had it, too
("this option is given"))).
--
Štěpán
next prev parent reply other threads:[~2023-08-28 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 10:42 [PATCH 1/5] ci/profiles.sh: fix case matching logic Štěpán Němec
2023-08-28 10:42 ` [PATCH 2/5] watch: remove unused variable Štěpán Němec
2023-08-28 10:42 ` [PATCH 3/5] spawn: remove stray variable $ndc_err Štěpán Němec
2023-08-28 10:42 ` [PATCH 4/5] spawn: remove distracting empty line Štěpán Němec
2023-08-28 10:42 ` [PATCH 5/5] Fix some typos/grammar/errors in docs and comments Štěpán Němec
2023-08-28 21:11 ` Eric Wong
2023-08-28 21:22 ` Štěpán Němec [this message]
2023-08-28 21:38 ` Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230828232247+0200.172961-stepnem@smrk.net \
--to=stepnem@smrk.net \
--cc=e@80x24.org \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).