Re: pgindent-polluted commits

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgindent-polluted commits
Date: 2016-01-14 16:32:38
Message-ID: CA+TgmobGKmt+DmZwLrcoHUhZnGgC5j7quWLh6dEvNy7HjAq+3w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 14, 2016 at 11:25 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> I do think it makes life easier when going through the git history if
> semantic changes are separated from formatting changes.

I agree. And I agree with Mark Dilger's point, too.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-01-14 16:38:41 Re: Python 3.x versus PG 9.1 branch
Previous Message Robert Haas 2016-01-14 16:31:03 Re: Performance degradation in commit ac1d794