Re: Maintaining a list of pgindent commits for "git blame" to ignore
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2021-03-18T23:54:53Z
Lists: pgsql-hackers
On Thu, Mar 18, 2021 at 4:40 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Good question. We don't have a standard about that (whether to > do those in separate or the same commits), but we could establish one > if it seems helpful. I don't think that it matters too much, but it will necessitate updating the file multiple times. It might become natural to just do everything together in a way that it wasn't before. The really big wins come from excluding the enormous pgindent run commits, especially for the few historic pgindent runs where the rules changed -- there are no more than a handful of those. They tend to generate an enormous amount of churn that touches almost everything. So it probably isn't necessary to worry about smaller things. -- Peter Geoghegan
Commits
-
Add list of ignorable pgindent commits for git-blame.
- 8e638845ff6b 14.0 landed
-
pgindent run prior to branching v13.
- b5d69b7c22ee 13.0 cited