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: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Run pgindent now?
Date: 2015-05-25 18:57:10
Message-ID: 20150525185710.GF3908@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 25, 2015 at 12:49:41PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2015-05-25 18:58:26 Re: Run pgindent now?
Previous Message Bruce Momjian 2015-05-25 18:55:54 Re: Run pgindent now?