From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: [9front] Patch: factotum(4) typos
Date: Thu, 9 Mar 2023 16:46:19 +0100 (GMT+01:00) [thread overview]
Message-ID: <304984b4-0070-45ae-8466-68858079af92@sirjofri.de> (raw)
Hey,
this patch fixes two typos I found while reading factotum(4).
sirjofri
--- snip snap ---
/sys/man/4/factotum:53,59 - /tmp/factotum.4:53,59
when read lists the protocols available
.TP
.B confirm
- for confiming the use of key
+ for confirming the use of key
.TP
.B needkey
allows external programs to control the addition of new keys
/sys/man/4/factotum:692,698 - /tmp/factotum.4:692,698
the write is too short, get more data from the
other party and retry the write.
.I n
- specifies the maximun total number of bytes.
+ specifies the maximum total number of bytes.
.TP
.B "phase \fIstring\fP
its not your turn to write, get some data from
next reply other threads:[~2023-03-09 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 15:46 sirjofri [this message]
2023-03-10 2:20 ` Alex Musolino
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=304984b4-0070-45ae-8466-68858079af92@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--cc=9front@9front.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).