Re: Run pgindent now?

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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 19:32:42
Message-ID: 20150526193242.GY5885@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:

> But every time we pgindent, especially with slightly different
> settings, we cause tools like 'git blame' to return less useful
> answers. And that sucks.

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.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2015-05-26 19:34:32 jsonb_set
Previous Message Tom Lane 2015-05-26 19:07:26 Re: Run pgindent now?