| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:50:56 |
| Message-ID: | 936adf70-abc1-254e-7fd7-14c40ccf9ff5@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/28/21 10:44 AM, Tom Lane wrote:
> I wrote:
>> Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2021-06-28 14:51:06 | Re: Can a child process detect postmaster death when in pg_usleep? |
| Previous Message | Daniel Gustafsson | 2021-06-28 14:45:53 | Re: Unbounded %s in sscanf |