Re: annoyance with .git-blame-ignore-revs - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: annoyance with .git-blame-ignore-revs
Date
Msg-id 81E49537-7334-472B-8C6C-529D8F781B7B@yesql.se
Whole thread Raw
In response to Re: annoyance with .git-blame-ignore-revs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On 11 Jul 2022, at 21:35, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Alvaro Herrera <alvherre@alvh.no-ip.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/




pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: annoyance with .git-blame-ignore-revs
Next
From: Peter Geoghegan
Date:
Subject: Re: annoyance with .git-blame-ignore-revs