On 21.10.2017 18:57, Peter Eisentraut wrote:
One workaround (other than being careful) would be to write
and maintain that style until the last SGML-based version goes EOL.
Another workaround would be to backpatch a check that greps for
something like '[^<]/>' in *.sgml and errors on tha
Hello,
21.10.2017 19:57, Peter Eisentraut wrote:
In a nearby message, Tom pointed out that the ongoing conversion of the
documentation sources from SGML to XML could/will cause problems when
backpatching. The changes made so far would merely cause merge
conflicts but there is an additional issue
Alexander Lakhin writes:
> 21.10.2017 19:57, Peter Eisentraut wrote:
>> In a nearby message, Tom pointed out that the ongoing conversion of the
>> documentation sources from SGML to XML could/will cause problems when
>> backpatching. The changes made so far would merely cause merge
>> conflicts b
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 closin
