From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Alexander Lakhin <exclusion@gmail.com>
To: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: backpatching documentation after conversion to XML
Date: Fri, 10 Nov 2017 08:51:55 -0500
Message-ID: <a85ccf75-e9f7-2cde-0624-3426f775cad6@2ndquadrant.com> (raw)
In-Reply-To: <b0fdbf01-430a-9f17-74f8-0ade0882954f@2ndquadrant.com>
References: <609dc528-6eab-522d-5b7d-842bd83159e5@2ndquadrant.com>
<dec8f417-4b42-4e4f-8dfd-d8256bb437b4@gmail.com>
<b0fdbf01-430a-9f17-74f8-0ade0882954f@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
On 11/3/17 14:29, Peter Eisentraut wrote:
>>> Another workaround would be to backpatch a check that greps for
>>> something like '[^<]/>' in *.sgml and errors on that.
> I have since figured out that the SP option -wnet will cause errors on
> XML-style empty tags, so I plan to proceed that way after the minor
> releases.
I have committed that.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, exclusion@gmail.com
Subject: Re: backpatching documentation after conversion to XML
In-Reply-To: <a85ccf75-e9f7-2cde-0624-3426f775cad6@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox