Re: Documentation and explanatory diagrams
От | Tom Lane |
---|---|
Тема | Re: Documentation and explanatory diagrams |
Дата | |
Msg-id | 11932.1308010495@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Documentation and explanatory diagrams (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: Documentation and explanatory diagrams
|
Список | pgsql-docs |
Bruce Momjian <bruce@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 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. regards, tom lane
В списке pgsql-docs по дате отправления: