| 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-23 16:13:35 |
| Message-ID: | 20150523161335.GB28512@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 22, 2015 at 12:02:11PM -0400, Tom Lane wrote:
> I guess in the
> scenario you're describing, the most helpful thing would be if the
> pgindent commit put the typedef list it had used into the tree, and then
> we just use that (plus manual additions) when generating the I' commit.
I have always added the typedef list I used as part of pgindent commit
runs.
Are we ready for a pgindent run? Back branches?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-23 16:32:34 | Re: Run pgindent now? |
| Previous Message | David E. Wheeler | 2015-05-23 15:59:02 | Re: jsonb_set: update or upsert default? |