On Mon, May 25, 2015 at 12:49:41PM -0400, Tom Lane wrote: > Bruce Momjian <br...@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 <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
