Re: pgindent vs. git whitespace check

From: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgindent vs. git whitespace check
Date: 2023-02-23 04:12:56
Message-ID: CAFBsxsF8yVH8iFsEbCO=fEcxotWG5oKNpD2+CqfLhkBwLqU9WA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 23, 2023 at 5:03 AM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> I suspect not allowing // is at least a minor annoyance to any new
developer we acquire under the age of about 40.

pgindent changes those to our style, so it's not much of an annoyance if
one prefers to type it that way during development.

--
John Naylor
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2023-02-23 04:40:01 RE: Allow logical replication to copy tables in binary format
Previous Message Tom Lane 2023-02-23 04:03:48 Re: Improving inferred query column names