Re: pgindent-polluted commits - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: pgindent-polluted commits
Date
Msg-id CAM3SWZSrGsLYv6KrWUQUeHf-Q4RtOz_-gvw-DyO+tDoj0ChVbQ@mail.gmail.com
Whole thread Raw
In response to Re: pgindent-polluted commits  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jan 13, 2016 at 9:13 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I'm willing to go with the "separate commit to reindent individual files"
> approach if there's a consensus that that makes for a cleaner git history.
> But I'm not 100% convinced it matters.

I recently changed the configuration of my text editor to
automatically use the "git blame" whitespace flag when using its git
plugin. I did this because there was a tendency for pgindent commits
to freeze everything for several seconds when I made the mistake of
looking at a pgindent commit diff. This approach seems to work nicely,
without any downside that I've noticed.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: WIP: Covering + unique indexes.
Next
From: Tom Lane
Date:
Subject: Re: pg_dump and premature optimizations for objects not to be dumped