| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: perltidy version |
| Date: | 2018-03-04 20:42:25 |
| Message-ID: | 9B86EB7D-6FE0-470F-B0CA-8A56161B8035@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 04 Mar 2018, at 00:03, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> Ah yeah, if I apply that one first, the diff from using 20140328 is much
>> smaller. Attached is that one, which means the difference between the two
>> perltidy versions.
>
> I'm hardly a Perl guru, so I'm not going to opine on whether these
> changes are for the better or worse. They're definitely not very
> extensive, though. If the folks here who do hack Perl a lot think
> the 20140328 output is better, I'm fine with switching.
The 20140328 format is, IMHO, better in enough ways that I’d recommend
switching. The fact that it makes download for users, and documentation
writing for the project, easier is another good thing. +1 for going ti
20140328.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-04 20:46:56 | Re: [HACKERS] user-defined numeric data types triggering ERROR: unsupported type |
| Previous Message | Andrew Dunstan | 2018-03-04 20:41:17 | Re: perltidy version |