| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgindent run |
| Date: | 2021-06-28 14:21:57 |
| Message-ID: | 153629.1624890117@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-06-28 14:44:42 | Re: pgindent run |
| Previous Message | Tom Lane | 2021-06-28 14:15:23 | Re: Remove redundant initializations |