Re: annoyance with .git-blame-ignore-revs
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-07-11T19:37:26Z
Lists: pgsql-hackers
On Mon, Jul 11, 2022 at 12:30 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > Anybody has any idea how to handle this better? > > A viable option would be to backpatch the addition of > .git-blame-ignore-revs to all live branches. Would that bother anyone? +1. I was thinking of suggesting the same thing myself, for the same reasons. This solution is a good start, but it does leave one remaining problem: commits from before the introduction of .git-blame-ignore-revs still won't have the file. There was actually a patch for git that tried to address the problem directly, but it didn't go anywhere. Maybe just backpatching the file is good enough. -- Peter Geoghegan
Commits
-
Backpatch addition of .git-blame-ignore-revs
- fff3f3333fdc 14.5 landed
- d7714c1454c3 16.0 landed
- c122a99bd6af 13.8 landed
- 743a7a10fb0c 10.22 landed
- 704fc3c8d080 12.12 landed
- 261f1a437288 15.0 landed
- 258a66aca920 11.17 landed