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

From Bruce Momjian
Subject Re: Run pgindent now?
Date
Msg-id 20150525185710.GF3908@momjian.us
Whole thread Raw
In response to Re: Run pgindent now?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, May 25, 2015 at 12:49:41PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > If we wanted to do this on backbranches, I think we would create a diff
> > file of the minor release just before running pgindent and stamping so
> > users could see the non-pgindent content of the release.
> 
> What for?  Those who want to see that can look at our git repo.

True.  I was just considering people who want a comprehensive diff.

> > A crazy idea
> > would be to release of just pgindent changes so we would not add
> > pgindent changes into a fix release.
> 
> I'm not entirely sure that I follow you here, but it doesn't sound very
> workable --- what happens when we go to back-patch changes in an area
> that was previously reindented?  You can't have two separate versions
> of a branch.

It would be a PG release, with number increment, which only has pgindent
changes.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: fsync-pgdata-on-recovery tries to write to more files than previously
Next
From: Tom Lane
Date:
Subject: Re: Run pgindent now?