| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Liudmila Mantrova <l(dot)mantrova(at)postgrespro(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: documentation is now XML |
| Date: | 2018-04-27 15:36:40 |
| Message-ID: | 27028.1524843400@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Fri, Apr 27, 2018 at 11:00:36AM -0400, Peter Eisentraut wrote:
>> That proposal seemed to indicate not only converting the source code to
>> XML but also the build system to XSL. The latter is out of the
>> question, I think.
> Why is that? I thought people building current Postgres would already
> have the XML toolchain built to build older release documentation.
Yeah, in principle, anyone who's able to build the v10 branch's docs
should be ready for such a change. We had discussed polling the
pgsql-packagers list to see whether anyone would have a problem with
changing the docs build toolset for the pre-v10 branches, but I don't
think we actually asked them.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2018-04-27 15:42:00 | Re: Add read-only param to set_config(...) / SET that effects (at least) customized runtime options |
| Previous Message | Andrew Gierth | 2018-04-27 15:35:31 | Re: Toast issues with OldestXmin going backwards |