From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: annoyance with .git-blame-ignore-revs |
Date: | 2022-07-11 19:37:26 |
Message-ID: | CAH2-Wz=4d2C-jDT2iR3fJBX2usLJhr2cHEp-j-f6tYscEn77ig@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 11, 2022 at 12:30 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2022-07-11 19:38:07 | Re: annoyance with .git-blame-ignore-revs |
Previous Message | Tom Lane | 2022-07-11 19:35:58 | Re: annoyance with .git-blame-ignore-revs |