From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, Thom Brown <thom(at)linux(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Documentation and explanatory diagrams |
Date: | 2011-06-14 12:54:22 |
Message-ID: | BANLkTikBHP73RT+Ead2GQmd+YzP02x3hQg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Mon, Jun 13, 2011 at 8:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> Tom Lane wrote:
>>> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>>> Perhaps we should allow any SVG file to be imported, but only allow
>>>> modifications by a single SVG editor.
>
>>> How is that sensible? The first change to the file will result in
>>> exactly the mass of cosmetic diffs that we wish to avoid.
>
>> I suggested this so we could get images into the docs and then only have
>> a single diff change once the file is modified. If we don't do that
>> then all image additions have to be done by someone with the proper
>> editor.
>
> Or at least, somebody passes it through the "proper editor" before
> committing. As long as said editor can read SVG output from a
> reasonable range of other tools, this doesn't seem that onerous.
Bad news, Bruce: you're going to have to learn a new tool. :-)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2011-06-14 12:59:41 | Re: Documentation and explanatory diagrams |
Previous Message | Bruce Momjian | 2011-06-14 00:58:03 | Re: CIDR address in pg_hba.conf |