Subject: Re: backpatching documentation after conversion to XML
To: Alexander Lakhin <exclusion@gmail.com>,
 pgsql-docs <pgsql-docs@postgresql.org>
References: <609dc528-6eab-522d-5b7d-842bd83159e5@2ndquadrant.com>
 <dec8f417-4b42-4e4f-8dfd-d8256bb437b4@gmail.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <b0fdbf01-430a-9f17-74f8-0ade0882954f@2ndquadrant.com>
Date: Fri, 3 Nov 2017 14:29:21 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <dec8f417-4b42-4e4f-8dfd-d8256bb437b4@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On 10/22/17 11:33, Alexander Lakhin wrote:
> Peter, are you going to rename all the *.sgml to *.xml (and to move the 
> files from sgml/ to /xml directory) as I did?

Not at the moment, but maybe later.  That can be a separate discussion.

> If so (I think it would be right), then backpatching without some 
> modifications will be impossible anyway.

git cherry-pick should be able to handle it.

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

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