From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: man.7 tweaks
Date: Sat, 24 Jul 2010 14:31:52 +0059 [thread overview]
Message-ID: <20100724133216.GA15380@bramka.kerhand.co.uk> (raw)
diff for some man.7 tweaks below. couple of questions:
*) openbsd doesn;t have a LIBRARY section. what is the best way to
reflect that? ingo?
*) (again ingo) how does this diff get committed?
*) unrelated, but i'm currently discussing the EXIT STATUS section with
daniel dickman:
EXIT STATUS
This section documents the command exit status for section
1, 6, and 8 utilities. Historically, this information was
described in DIAGNOSTICS, a practise that is now discouraged.
says who? i mean, what leads you to believe this? i ask because openbsd
has no EXIT STATUS section, and both netbsd and freebsd have this in
their groff_man(7) pages:
.Sh DIAGNOSTICS
Diagnostic messages from a command should be placed in this
section. The `.Ex' macro may be used to generate text for
use in the DIAGNOSTICS section for most section 1, 6 and
8 commands; see Exit Status.
i'm trying to work out what the best way forward is.
jmc
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2010-07-24 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 13:32 Jason McIntyre [this message]
2010-07-24 13:59 ` Ingo Schwarze
2010-07-24 14:51 ` Jason McIntyre
2010-07-24 18:47 ` Ingo Schwarze
2010-07-24 15:04 ` Jason McIntyre
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=20100724133216.GA15380@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).