| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: backpatching documentation after conversion to XML |
| Date: | 2017-11-03 18:29:21 |
| Message-ID: | b0fdbf01-430a-9f17-74f8-0ade0882954f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-11-04 18:47:12 | Re: Behavior of recovery_target_inclusive. |
| Previous Message | hmidi slim | 2017-11-03 13:14:19 | Explain the difference between ts_rank and ts_rank_cd |