From: Alexander Lakhin <exclusion@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: backpatching documentation after conversion to XML
Date: Sun, 22 Oct 2017 21:00:06 +0300
Message-ID: <8bb5a579-5a9d-3aad-7b27-275b0b9bb4c2@gmail.com> (raw)
In-Reply-To: <14052.1508690564@sss.pgh.pa.us>
References: <609dc528-6eab-522d-5b7d-842bd83159e5@2ndquadrant.com>
<dec8f417-4b42-4e4f-8dfd-d8256bb437b4@gmail.com>
<14052.1508690564@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
22.10.2017 19:42, Tom Lane writes:
>> I think we should make a script to backport doc/-related commits.
> That's an interesting idea, but I really doubt that you'll be able
> to make a script that copes with this without having back-patched
> the changes we're discussing. As an example, any given closing tag
> might've already been spelled out in the back branches; we've never
> been consistent about that. So you couldn't just automatically
> shorten all the closing tags and expect to have a patch that applies.
I understand the major difficulties we have to deal with. I have the
following plan in mind:
1. Get a diff for a single xml.
2. Find corresponding sgml in the old target branch.
3. Convert the sgml to xml following the same procedure that we applied
for the master branch.
4. Try to apply the diff.
5. If it's applied successfully, detect the lines where changes occured
(sgml->xml conversion doesn't move the lines) and
modify corresponding lines in sgml with the content modified for sgml
(<xref .../> changed to <xref > and so on.)
I think this should work for 90% of cases.
------
Alexander Lakhin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
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: exclusion@gmail.com, tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com
Subject: Re: backpatching documentation after conversion to XML
In-Reply-To: <8bb5a579-5a9d-3aad-7b27-275b0b9bb4c2@gmail.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