Re: Run pgindent now? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Run pgindent now?
Date
Msg-id CA+TgmoYfnvZ8X6s8oyL2BcMO6xLUSXRU1srH3dok7Q4nBbcUVg@mail.gmail.com
Whole thread Raw
In response to Re: Run pgindent now?  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Run pgindent now?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, May 18, 2015 at 12:10 PM, Bruce Momjian <bruce@momjian.us> wrote:
> On Sat, May 16, 2015 at 01:05:27PM -0400, Tom Lane wrote:
>> Magnus Hagander <magnus@hagander.net> writes:
>> > On Sat, May 16, 2015 at 5:58 PM, Tom Lane <tgl@sss.pgh.pa.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?

I am personally not excited about that.  I would rather leave the
back-branches alone.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Bruno Harbulot
Date:
Subject: Re: Problems with question marks in operators (JDBC, ECPG, ...)
Next
From: "David G. Johnston"
Date:
Subject: Re: Problems with question marks in operators (JDBC, ECPG, ...)