Re: annoyance with .git-blame-ignore-revs

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: annoyance with .git-blame-ignore-revs
Date: 2022-07-11 19:38:07
Message-ID: 81E49537-7334-472B-8C6C-529D8F781B7B@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 11 Jul 2022, at 21:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
>> A viable option would be to backpatch the addition of
>> .git-blame-ignore-revs to all live branches. Would that bother anyone?
>
> Only if we had to update all those copies all the time. But
> I'm guessing we wouldn't need a branch's copy to be newer than
> the last pgindent run affecting that branch?

We shouldn't need that, if we do it would indicate we did cosmetic-only commits
in backbranches which IIUC isn't in line with project policy (or at least rare
to the point of not being a problem).

--
Daniel Gustafsson https://vmware.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2022-07-11 19:39:48 Re: annoyance with .git-blame-ignore-revs
Previous Message Peter Geoghegan 2022-07-11 19:37:26 Re: annoyance with .git-blame-ignore-revs