| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Run pgindent now? |
| Date: | 2015-05-26 21:19:42 |
| Message-ID: | 20150526211942.GH5310@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-05-26 16:32:42 -0300, Alvaro Herrera wrote:
> I've wondered a few times whether there's a way to make pgindent commits
> "transparent" to git blame, i.e. blame their modified lines to whatever
> commits modified them immediately before.
You can make blame ignore whitespace changes with -w -- but that
obviously doesn't help with rewrapped lines and such.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oskari Saarenmaa | 2015-05-26 21:19:51 | Re: hstore_plpython regression test does not work on Python 3 |
| Previous Message | Aidan Van Dyk | 2015-05-26 21:13:08 | Re: Run pgindent now? |