Re: Maintaining a list of pgindent commits for "git blame" to ignore - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Maintaining a list of pgindent commits for "git blame" to ignore
Date
Msg-id CAH2-Wzn=JRwVMPOmYB7v+YzEWnesTqDCqmo26-Bqbx1YeHM-hg@mail.gmail.com
Whole thread Raw
In response to Re: Maintaining a list of pgindent commits for "git blame" to ignore  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Thu, Mar 18, 2021 at 4:00 PM Bruce Momjian <bruce@momjian.us> wrote:
> Probably because later commits might collide with shorter hashes.  When
> you are reporting a hash that only looks _backward_, this is not an
> issue.

Right, but it's extremely unlikely to happen by accident. I was
suggesting that there might be a security issue. I could fairly easily
make my git commit match a prefix intended to uniquely identify your
git commit if I set out to do so.

There are projects that might have to consider that possibility,
though perhaps we're not one of them.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Maintaining a list of pgindent commits for "git blame" to ignore
Next
From: Tom Lane
Date:
Subject: Re: Maintaining a list of pgindent commits for "git blame" to ignore