|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Bruce Momjian <bruce(at)momjian(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?|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
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.
> 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.
regards, tom lane
|Next Message||Tom Lane||2015-05-25 17:10:04||Re: Run pgindent now?|
|Previous Message||Uriy Zhuravlev||2015-05-25 16:44:57||Re: WIP: Enhanced ALTER OPERATOR|