Re: Maintaining a list of pgindent commits for "git blame" to ignore

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Maintaining a list of pgindent commits for "git blame" to ignore
Date: 2021-06-22 15:15:39
Message-ID: CAH2-WznRDB9O-nKd6YOD1nRhDnE1KOeV2Y42AS-Na7QSeJ_i3w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 22, 2021 at 8:04 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Hmm, is the "git config blame.ignoreRevsFile" setting actually
> repo-relative? I'm a bit confused as to whether an absolute
> file path would be needed to ensure correct behavior.

That seems to be standard practice, and certainly works for me.

If any of the hashes are not well formed, or even appear in
abbreviated form, "git blame" breaks in a very obvious and visible
way. So there is zero chance of it breaking without somebody noticing
immediately.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-06-22 15:18:05 Re: Maintaining a list of pgindent commits for "git blame" to ignore
Previous Message Maxim Orlov 2021-06-22 15:06:49 Re: Parallel scan with SubTransGetTopmostTransaction assert coredump