| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org, Jürgen Purtz <juergen(at)purtz(dot)de> |
| Subject: | Re: First SVG graphic |
| Date: | 2019-03-14 13:10:42 |
| Message-ID: | 23265.1552569042@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> On 2019-03-11 15:50, Tom Lane wrote:
>> Ideally, we'd treat them much as we do for bison output files:
>> we'll supply them in tarballs but you'd better have the relevant
>> tools if you want to build docs from a git pull. However, that
>> may be assuming too much about the portability of the tools ...
> The portability is not something I'm concerned about, but Ditaa requires
> Java, so that might annoy some people.
Portability is something you *should* be concerned about. We want
all patch submitters to be able to build the docs, else we'll forever
be fighting silly markup errors. That's not a productive use of
anybody's time.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2019-03-14 15:29:04 | 28.4.1. VACUUM Progress Reporting |
| Previous Message | Peter Eisentraut | 2019-03-14 12:40:38 | Re: First SVG graphic |