From: fig <type9freak@gmail.com>
To: 9front@9front.org
Subject: [9front] [patch] upasfs(4) fix
Date: Thu, 12 Jan 2023 22:11:25 -0800 [thread overview]
Message-ID: <CANF_3Rg5Nt27FhEjTQOvatbATQx5i+R5Qu7+1qRxH3D+vrEN_g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
this fixes upasfs(4) referencing itself, and trailing comma.
diff 0e66f87316e571f7edf5274369ec69a5905507aa uncommitted
--- a/sys/man/4/upasfs
+++ b/sys/man/4/upasfs
@@ -474,8 +474,7 @@
.IR pop3 (8),
.IR qer (8),
.IR rewrite (6),
-.IR send (8),
-.IR upasfs (4),
+.IR send (8)
.br
Erik Quanstrom
``Scaling Upas'',
[-- Attachment #2: Type: text/html, Size: 512 bytes --]
next reply other threads:[~2023-01-13 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 6:11 fig [this message]
2023-01-13 12:57 ` 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=CANF_3Rg5Nt27FhEjTQOvatbATQx5i+R5Qu7+1qRxH3D+vrEN_g@mail.gmail.com \
--to=type9freak@gmail.com \
--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).