tech@mandoc.bsd.lv
 help / color / Atom feed
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: Mon, 16 Mar 2020 11:01:15 +0100
Message-ID: <20200316100115.GC40425@athene.usta.de> (raw)
In-Reply-To: <CAGw6cBs6nNpNAHah=e-mC=qi0n50ar8RE=7U5JL6dGmuCQ4sTw@mail.gmail.com>

Hi Michael,

Michael Forney wrote on Tue, Mar 03, 2020 at 07:50:52PM -0800:
> On 2020-03-03, Ingo Schwarze <schwarze@usta.de> wrote:

>> 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.

> I'm aware that it's just a bug fix release, but it is a version of the
> standard nonetheless, so I thought it would be useful to be able to
> refer to it.
> 
> IEEE Std 1003.1-2004 is also just the incorporation of a couple TCs
> into 1003.1-2001, yet it is supported by mandoc. I don't really see
> the difference between that case and 1003.1-2017.

It is harder to undo errors made in the past than to avoid similar
errors in the future.

It would be good to delete .St -p1003.1-2004, but that would require
hunting down the instances where it is used in all the BSD systems
first.  For example, in OpenBSD, it is still used in six pages,
and it is used by mistake in every single case.

In FreeBSD, it is used about 30 times, in NetBSD about 80 times.
And then there are DragonFly and illumos.
Doing that work such that it can be cleaned up is not high priority.

>> Besides, this has already been discussed repeatedly.

> Sorry about that, I didn't know this had already been discussed (I
> wasn't able to find any mailing list archives).

I tried to get the mandoc lists into marc.info, but never got a response
from the maintainers of that service, and i never came round to set up
my own web archive.  It would certainly be useful.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv

      reply index

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
2020-03-04  3:50   ` Michael Forney
2020-03-16 10:01     ` Ingo Schwarze [this message]

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=20200316100115.GC40425@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

tech@mandoc.bsd.lv

Archives are clonable: git clone --mirror http://inbox.vuxu.org/mandoc-tech

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.mandoc.tech


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git