Tom Lane wrote: > Bruce Momjian <br...@momjian.us> 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 <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
