From: Romano <me+unobe@fallglow.com>
To: 9front@9front.org
Subject: [9front] [PATCH] 9p(2) minor typos
Date: Sun, 30 Jun 2024 06:46:33 +0000 [thread overview]
Message-ID: <3E4AF32A3534D9DC521F350C640D2079@smtp.pobox.com> (raw)
---
diff 559725a4c1048cb88e44cbb7a15d1c7990d2e465 f12775c520326e2c300a3346a7deb1a777a9e4f6
--- a/sys/man/2/9p
+++ b/sys/man/2/9p
@@ -241,8 +241,8 @@
.B RFNOTEG
and
.B RFMEM
-flags. This isolates the service loop from the callers
-namespace and from notes posted to the callers note group
+flags. This isolates the service loop from the caller's
+namespace and from notes posted to the caller's note group
but shares data and bss segments.
.IP
The child process then waits for the parent to copy its
@@ -849,7 +849,7 @@
authenticated or will return -1 and
call
.I respond
-with an apropiate error.
+with an appropriate error.
.I Authread
and
.I authwrite
reply other threads:[~2024-06-30 6:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E4AF32A3534D9DC521F350C640D2079@smtp.pobox.com \
--to=me+unobe@fallglow.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).