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:32:20Z
Lists: pgsql-hackers
On Thu, Mar 18, 2021 at 4:05 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > b5d69b7c22ee4c44b8bb99cfa0466ffaf3b5fab9 # Sun Jun 7 16:57:08 2020 -0400 > # pgindent run prior to branching v13. > > which is easy to make from "git log" or "git show" output. (Because > of the precedent of those tools, I'd rather write the commit hash > before the rest of the entry.) WFM. What about reformat-dat-files and perltidy runs? It seems that you have sometimes used all three reformatting tools to produce one commit -- but not always. ISTM that I should get any of those that I missed. And that the pgindent README (which already mentions these other tools) ought to be updated to be explicit about the policy applying equally to commits that apply any of the two other tools in bulk. -- 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