Re: pgindent run - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgindent run
Date
Msg-id 153629.1624890117@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgindent run  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pgindent run
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 6/28/21 8:52 AM, David Rowley wrote:
>> I wasn't too sure about the status of this one. Michael did mention it
>> in [1], but Tom mentioned that was on purpose to ease backpatching.
>> I'm not too clear on if Tom intended it should stay unindented until
>> "rewriting that whole function in a little bit".

> 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.

            regards, tom lane

[1] https://www.postgresql.org/message-id/1573181.1624220108%40sss.pgh.pa.us



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Remove redundant initializations
Next
From: Tom Lane
Date:
Subject: Re: pgindent run