public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Tom Lane <[email protected]>
Cc: Ross J. Reedstrom <[email protected]>
Cc: Thom Brown <[email protected]>
Cc: Greg Smith <[email protected]>
Cc: [email protected]
Subject: Re: Documentation and explanatory diagrams
Date: Mon, 13 Jun 2011 20:34:03 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Tom Lane wrote:
> Bruce Momjian <[email protected]> writes:
> > I think the big question is whether we can afford to allow multiple SVG
> > editor file formats to be checked in, and hence support git diff churn
> > as we switch SVG editors for commits.  This doesn't seem likely to
> > improve anytime soon so we should just decide and move forward.
> 
> > 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.

> I think we probably have to specify the One True Graphics Editor, and
> maybe even specific version(s) of it, if we want to avoid unreadable
> diffs.  The reason we have not managed to come to a consensus yet is
> that people would prefer not to do that, but it's becoming obvious that
> there just isn't any way around it.

Yes.

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

view thread (114+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Documentation and explanatory diagrams
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox