From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Liudmila Mantrova <l(dot)mantrova(at)postgrespro(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: documentation is now XML |
Date: | 2018-04-27 15:03:06 |
Message-ID: | 20180427150306.GC32454@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 27, 2018 at 11:00:36AM -0400, Peter Eisentraut wrote:
> On 4/23/18 05:54, Liudmila Mantrova wrote:
> > Reading this thread, I got an impression that everyone would benefit
> > from converting back branches to XML, but the main concern is lack of
> > resources to complete this task. Are there any other issues that affect
> > this decision? Looks like Aleksander Lakhin's offer to prepare patches
> > was missed somehow as the discussion sidetracked to other issues
>
> 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.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Konstantin Knizhnik | 2018-04-27 15:05:51 | Re: Built-in connection pooling |
Previous Message | Robert Haas | 2018-04-27 15:03:01 | Re: Toast issues with OldestXmin going backwards |