Re: pgindent vs. git whitespace check
От
Bruce Momjian
Тема
Re: pgindent vs. git whitespace check
Дата
Msg-id
ZCWhOdUUqKBWIabu@momjian.us
Ответ на
Re: pgindent vs. git whitespace check (Daniel Gustafsson)
Список
Дерево обсуждения
pgindent vs. git whitespace check Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: pgindent vs. git whitespace check Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: pgindent vs. git whitespace check Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: pgindent vs. git whitespace check Tom Lane <tgl@sss.pgh.pa.us>
Re: pgindent vs. git whitespace check Andrew Dunstan <andrew@dunslane.net>
Re: pgindent vs. git whitespace check John Naylor <john.naylor@enterprisedb.com>
Re: pgindent vs. git whitespace check Tom Lane <tgl@sss.pgh.pa.us>
Re: pgindent vs. git whitespace check Daniel Gustafsson <daniel@yesql.se>
Re: pgindent vs. git whitespace check Bruce Momjian <bruce@momjian.us>
Re: pgindent vs. git whitespace check Daniel Gustafsson <daniel@yesql.se>
Re: pgindent vs. git whitespace check Bruce Momjian <bruce@momjian.us>
Re: pgindent vs. git whitespace check Andrew Dunstan <andrew@dunslane.net>
On Wed, Mar 29, 2023 at 08:26:23PM +0200, Daniel Gustafsson wrote: > > On 29 Mar 2023, at 19:18, Bruce Momjian wrote: > > We would have to convert all supported branches, and tell all forks to > > do the same (hopefully at the same time). The new standard would then > > be for all single-line comments to use // instead of /* ... */. > > That still leaves every patch which is in flight on -hackers, and conflicts in > local development trees etc. It's doable (apart from forks, but that cannot be > our core concern), but I personally can't see the price paid justify the result. Yes, this would have to be done at the start of a new release cycle. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Embrace your flaws. They make you human, rather than perfect, which you will never be.
В списке pgsql-hackers по дате отправления