From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Subject: [9front] [PATCH] segment(3): restore missing phrase
Date: Sat, 26 Jun 2021 17:18:49 -0700 [thread overview]
Message-ID: <YNfD6cKipGBEtfsk@alice> (raw)
It was accidentally removed when documenting
the sticky segment type in commit 99ed9623b.
---
diff 1e721f31f56c90e2586ff3b16ec2834677a899ef f879d1c76360234399d2497112b49cfb8c8d9b9e
--- a/sys/man/3/segment Mon Jun 21 01:23:43 2021
+++ b/sys/man/3/segment Sat Jun 26 17:16:31 2021
@@ -81,6 +81,7 @@
.B sticky
segments.
.PP
+When the segment is attached using
.IR segattach,
the address and length arguments are ignored in the call;
they are defined only by the
next reply other threads:[~2021-06-27 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 0:18 Anthony Martin [this message]
2021-06-27 0:52 ` ori
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=YNfD6cKipGBEtfsk@alice \
--to=ality@pbrane.org \
--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).