From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: rename sgml files? |
Date: | 2018-02-12 23:31:14 |
Message-ID: | 20180212233114.GG25321@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Feb 12, 2018 at 04:19:48PM -0500, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> > So, should we rename the *.sgml files to *.xml, since they are actually
> > now XML files?
>
> At that point, back-patching documentation fixes would become effectively
> impossible except through manual intervention in the patching process.
> I don't want to go there. The recent changes have already imposed a
> significant PITA factor on generating minor-release notes, and this
> would push it past what I care to deal with.
>
> As I've remarked before, the issue would disappear if we were to
> back-patch the XML-ization of the documentation. So I'd be fine
> with this if we did it uniformly in the supported branches. Otherwise
> I think the costs outweigh the benefits.
+1 for back-patching.
Are there scripts for (at least the first cut of) this?
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2018-02-12 23:34:52 | Re: Disabling src/test/[ssl|ldap] when not building with SSL/LDAP support |
Previous Message | Sand Stone | 2018-02-12 23:22:04 | Re: persistent read cache |