Re: pgindent run next week? - Mailing list pgsql-hackers

From Euler Taveira
Subject Re: pgindent run next week?
Date
Msg-id CAHE3wgh3VgMXTzJR-47=PjjOX-084ewMf23D30QQtAVzs0bL9w@mail.gmail.com
Whole thread Raw
In response to Re: pgindent run next week?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Em qua, 22 de mai de 2019 às 14:08, Tom Lane <tgl@sss.pgh.pa.us> escreveu:
>
> I wrote:
> > Hearing no objections, I'll plan on running pgindent tomorrow sometime.
>
> And done.
>
> > The new underlying pg_bsd_indent (2.1) is available now from
> > https://git.postgresql.org/git/pg_bsd_indent.git
>
> Please update your local copy if you have one.
>
I give it a try in a fork of PostgreSQL 10. The difference between v10
and my fork is not huge. The stats are 56 files changed, 2240
insertions(+), 203 deletions(-) and patch size is 139 Kb. I have
conflicts in 3 of 19 .h files and 1 of 25 .c files. Like Mark, I don't
have a strong preference, however, re-indent files would reduce
developer time while preparing patches to back branches.


--
   Euler Taveira                                   Timbira -
http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: Is it safe to ignore the return value of SPI_finish and SPI_execute?
Next
From: Tom Lane
Date:
Subject: Re: Remove useless associativity/precedence from parsers