[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bad signature on commit 6a34f4ccc8a5d (gnu: python-prompt-toolkit: U
|
From: |
Leo Famulari |
|
Subject: |
Re: Bad signature on commit 6a34f4ccc8a5d (gnu: python-prompt-toolkit: Update to 1.0.9.) |
|
Date: |
Thu, 29 Dec 2016 01:44:59 -0500 |
|
User-agent: |
Mutt/1.7.2 (2016-11-26) |
On Thu, Dec 29, 2016 at 07:08:18AM +0100, John Darrington wrote:
> How did these commits get into the repository? Our repository is
> configured to reject unsigned commits. Can it be that it doesn't
> actually check that the signature matches? !!!
Here's a pre-push Git hook that should prevent unsigned commits from
being pushed to any remote. I'd like to improve it to be applied
selectively per-remote.
pre-push
Description: Text document
signature.asc
Description: PGP signature