Re: pgindent run - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pgindent run
Date
Msg-id 936adf70-abc1-254e-7fd7-14c40ccf9ff5@dunslane.net
Whole thread Raw
In response to Re: pgindent run  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgindent run
List pgsql-hackers
On 6/28/21 10:44 AM, Tom Lane wrote:
> I wrote:
>> Andrew Dunstan <andrew@dunslane.net> writes:
>>> I'll let Tom speak for himself, but I somewhat doubt he meant the code
>>> to stay badly indented for more than a short period of time.
>> I did not.  If you can give me an hour or so, I'll get the patch
>> I previously proposed [1] committed, and then this issue will go away.
> Wait ... I did already, at 5a0f1c8c0.  Are you sure you were indenting
> current HEAD?
>
>             



No, see revised patch. I posted at 10.13


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Unbounded %s in sscanf
Next
From: Bharath Rupireddy
Date:
Subject: Re: Can a child process detect postmaster death when in pg_usleep?