| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jelte Fennema <postgres(at)jeltef(dot)nl>, Peter Geoghegan <pg(at)bowt(dot)ie>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Jesse Zhang <sbjesse(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: run pgindent on a regular basis / scripted manner |
| Date: | 2023-02-04 14:20:26 |
| Message-ID: | 118f5f43-25a0-43aa-7d9b-021aa53462eb@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-02-04 Sa 06:34, Andres Freund wrote:
>
> ISTM that we're closer to being able to enforce pgindent than
> perltidy. At the same time, I think the issue of C code in HEAD not
> being indented is more pressing - IME it's much more common to have to
> touch a lot of C code than to have to touch a lot fo perl files. So
> perhaps we should just start with being more stringent with C code, and
> once we made perltidy less noisy, add that?
>
Sure, we don't have to tie them together.
I'm currently experimenting with settings on the buildfarm code, trying
to get it both stable and looking nice. Then I'll try on the Postgres
core code and post some results.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2023-02-04 15:27:49 | Re: First draft of back-branch release notes is done |
| Previous Message | Daniel Verite | 2023-02-04 13:41:18 | Re: Allow tailoring of ICU locales with custom rules |