From: Ingo Schwarze <schwarze@usta.de>
To: Michael Forney <mforney@mforney.org>
Cc: tech@mandoc.bsd.lv
Subject: Re: [PATCH] Add POSIX.1-2017 to St macro
Date: Wed, 4 Mar 2020 03:56:51 +0100 [thread overview]
Message-ID: <20200304025651.GB50848@athene.usta.de> (raw)
In-Reply-To: <20200304021644.3512-1-mforney@mforney.org>
Hi Michael,
Michael Forney wrote on Tue, Mar 03, 2020 at 06:16:44PM -0800:
> Index: st.c
> ===================================================================
> RCS file: /cvs/mandoc/st.c,v
> retrieving revision 1.16
> diff -u -r1.16 st.c
> --- st.c 14 Dec 2018 01:18:26 -0000 1.16
> +++ st.c 4 Mar 2020 01:56:06 -0000
> @@ -37,6 +37,7 @@
> LINE("-p1003.1-2001", "IEEE Std 1003.1-2001 (\\(lqPOSIX.1\\(rq)")
> LINE("-p1003.1-2004", "IEEE Std 1003.1-2004 (\\(lqPOSIX.1\\(rq)")
> LINE("-p1003.1-2008", "IEEE Std 1003.1-2008 (\\(lqPOSIX.1\\(rq)")
> +LINE("-p1003.1-2017", "IEEE Std 1003.1-2017 (\\(lqPOSIX.1\\(rq)")
> LINE("-p1003.1", "IEEE Std 1003.1 (\\(lqPOSIX.1\\(rq)")
> LINE("-p1003.1b", "IEEE Std 1003.1b (\\(lqPOSIX.1b\\(rq)")
> LINE("-p1003.1b-93", "IEEE Std 1003.1b-1993 (\\(lqPOSIX.1b\\(rq)")
No, absolutely not. That is not a new version of POSIX, it is
merely the incorporation of a technical corrigendum. Manual pages
ought to continue referncing -p1003.1-2008.
In those very rare cases where the TC might require code changes,
those code changes can usually be considered bug fixes but do not
change how the related features are supposed to work and how they
need to be documented.
Even if a handful of manual pages need to reference the TC, for
example to make it explicit that the program in questions conforms
to some changed behaviour required by the TC, that doesn't require
a dedicated macro. Such an unusual case ought to be described more
explicitly if it really matters and not only by changing a number
that most readers will almost certainly overlook. And i haven't
even seen a single example yet where discussing the TC in a manual
page might be required...
Besides, this has already been discussed repeatedly.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2020-03-04 2:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 2:16 Michael Forney
2020-03-04 2:56 ` Ingo Schwarze [this message]
2020-03-04 3:50 ` Michael Forney
2020-03-16 10:01 ` Ingo Schwarze
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=20200304025651.GB50848@athene.usta.de \
--to=schwarze@usta.de \
--cc=mforney@mforney.org \
--cc=tech@mandoc.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).