Re: Run pgindent now?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Run pgindent now?
Date: 2015-05-18 16:10:31
Message-ID: 20150518161031.GA5282@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, May 16, 2015 at 01:05:27PM -0400, Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > On Sat, May 16, 2015 at 5:58 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> With feature freeze behind us, I'd like to propose that now is a good
> >> time for a pgindent run.
>
> > +1, except I suggest we at least delay it until we have wrapped the new
> > minor releases, to make sure we don't conflict with any backpatching there.
>
> Sure, a couple of days won't make much difference.

There was talk last time of pgindent-ing head and all back branches,
because a patch applied to head and back branches was historically only
pgindented in head, meaning that any future patches in that area could
not be easily backpatched.

Do we want to do this?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2015-05-18 16:21:14 Re: 9.5 open items
Previous Message Ryan Pedela 2015-05-18 15:57:41 Re: jsonb concatenate operator's semantics seem questionable