From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] public-inbox-netd: a multi-protocol superserver
Date: Sat, 7 May 2022 00:10:07 +0000 [thread overview]
Message-ID: <20220507001007.M914616@dcvr> (raw)
In-Reply-To: <87levfv7hs.fsf@kyleam.com>
Kyle Meyer <kyle@kyleam.com> wrote:
> s/may concatenated/may be concatenated/
>
> (It looks like -imapd and -nntpd pods have the same text, and both of
> those are also missing this "be".)
Thanks, will push this out, as well:
-------8<------
Subject: [PATCH] doc: add missing "be" for --key description
Link: https://public-inbox.org/meta/87levfv7hs.fsf@kyleam.com/
Noticed-by: Kyle Meyer <kyle@kyleam.com>
---
Documentation/public-inbox-imapd.pod | 2 +-
Documentation/public-inbox-netd.pod | 2 +-
Documentation/public-inbox-nntpd.pod | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/public-inbox-imapd.pod b/Documentation/public-inbox-imapd.pod
index 52df4d51..23577a69 100644
--- a/Documentation/public-inbox-imapd.pod
+++ b/Documentation/public-inbox-imapd.pod
@@ -54,7 +54,7 @@ automatically gets STARTTLS support.
The default private TLS certificate key for optional STARTTLS and IMAPS
support if the C<key> option is not given with C<--listen>. The private
-key may concatenated into the path used by C<--cert>, in which case this
+key may be concatenated into the path used by C<--cert>, in which case this
option is not needed.
=back
diff --git a/Documentation/public-inbox-netd.pod b/Documentation/public-inbox-netd.pod
index d6520608..dcf4d5b0 100644
--- a/Documentation/public-inbox-netd.pod
+++ b/Documentation/public-inbox-netd.pod
@@ -41,7 +41,7 @@ if the C<cert> option is not given with C<--listen>.
The default private TLS certificate key for optional TLS support
if the C<key> option is not given with C<--listen>. The private
-key may concatenated into the path used by C<--cert>, in which case this
+key may be concatenated into the path used by C<--cert>, in which case this
option is not needed.
=back
diff --git a/Documentation/public-inbox-nntpd.pod b/Documentation/public-inbox-nntpd.pod
index 651428ab..cf53da59 100644
--- a/Documentation/public-inbox-nntpd.pod
+++ b/Documentation/public-inbox-nntpd.pod
@@ -53,7 +53,7 @@ automatically gets STARTTLS support.
The default private TLS certificate key for optional STARTTLS and NNTPS
support if the C<key> option is not given with C<--listen>. The private
-key may concatenated into the path used by C<--cert>, in which case this
+key may be concatenated into the path used by C<--cert>, in which case this
option is not needed.
=back
prev parent reply other threads:[~2022-05-07 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 10:55 [PATCH] public-inbox-netd: a multi-protocol superserver Eric Wong
2022-05-06 0:18 ` Kyle Meyer
2022-05-07 0:10 ` Eric Wong [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
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=20220507001007.M914616@dcvr \
--to=e@80x24.org \
--cc=kyle@kyleam.com \
--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.
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).