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

From Tom Lane
Subject Re: Run pgindent now?
Date
Msg-id 5296.1432307372@sss.pgh.pa.us
Whole thread Raw
In response to Re: Run pgindent now?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Run pgindent now?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Robert Haas wrote:
>> On Tue, May 19, 2015 at 10:26 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> To do it before every minor release would require re-indenting HEAD
>>> as well (since the whole point is to keep HEAD and the back branches
>>> consistent).  I think we'd get too much push-back from developers
>>> whose pending patches got broken.  We can get away with reindenting
>>> HEAD between development cycles, but probably not more often than that.

>> I'm not convinced of that.  If we did it more often, it might actually
>> be less disruptive.

> I believe it's possible to mechanically rebase a patch over an indent
> run of the underlying branch with half a dozen commands or less.  +1 for
> reindenting all branches before each minor release, FWIW.

Yeah?  Can you show an example?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Run pgindent now?
Next
From: Tom Lane
Date:
Subject: Re: Add a hint when postgresql.conf hot_standby = 'off' and recovery.conf standby = 'on'