From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: EXIT STATUS for section 6
Date: Fri, 3 Sep 2010 13:57:19 +0100 [thread overview]
Message-ID: <20100903125743.GG9076@bramka.kerhand.co.uk> (raw)
the templates say EXIT STATUS is for sections 1 and 8. the descriptions
of EXIT STATUS say it is for sections 1, 6, and 8. which is it?
openbsd has no exit status info in any of its section 6 pages. ok?
jmc
Index: man.7
===================================================================
RCS file: /cvs/src/share/man/man7/man.7,v
retrieving revision 1.8
diff -u -r1.8 man.7
--- man.7 31 Aug 2010 17:51:31 -0000 1.8
+++ man.7 3 Sep 2010 12:56:15 -0000
@@ -306,7 +306,7 @@
the file is used (created, modified, etc.).
.It Em EXIT STATUS
This section documents the command exit status for
-section 1, 6, and 8 utilities.
+section 1 and 8 utilities.
Historically, this information was described in
.Em DIAGNOSTICS ,
a practise that is now discouraged.
Index: mdoc.7
===================================================================
RCS file: /cvs/src/share/man/man7/mdoc.7,v
retrieving revision 1.50
diff -u -r1.50 mdoc.7
--- mdoc.7 31 Aug 2010 17:51:31 -0000 1.50
+++ mdoc.7 3 Sep 2010 12:56:18 -0000
@@ -518,7 +518,7 @@
.Sx \&Pa .
.It Em EXIT STATUS
This section documents the
-command exit status for section 1, 6, and 8 utilities.
+command exit status for section 1 and 8 utilities.
Historically, this information was described in
.Em DIAGNOSTICS ,
a practise that is now discouraged.
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2010-09-03 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20100903-145809-+038.18-1@spamfilter.osbf.lua>
2010-09-03 12:57 ` Jason McIntyre [this message]
2010-09-03 16:29 ` Thomas Klausner
2010-09-03 19:28 ` Jason McIntyre
2010-09-03 22:42 ` Ingo Schwarze
2010-09-04 6:52 ` Jason McIntyre
2010-09-04 17:22 ` Kristaps Dzonsons
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=20100903125743.GG9076@bramka.kerhand.co.uk \
--to=jmc@kerhand.co.uk \
--cc=discuss@mdocml.bsd.lv \
/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).