[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: pre-push signature hook error reporting [was Re: [PATCH v6] gnu: pyt
Re: pre-push signature hook error reporting [was Re: [PATCH v6] gnu: python-sphinx: Update to 1.4.8.]
Fri, 20 Jan 2017 15:05:42 +0100
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
Leo Famulari <address@hidden> skribis:
> On Fri, Jan 13, 2017 at 10:24:00AM -0500, Leo Famulari wrote:
>> I bet that you are using the new pre-push hook that verifies commit
>> signatures, and you're trying to push some commits that fail the
>> signature verification check.
>> Someone should add some error reporting to the hook.
> In Git 2.11.0, it seems that `git verify-commit` can't tell the user
> which commits failed verification:
> With a warm cache and all the public keys on my machine, checking the
> signature of all 17813 commits on the master branch takes ~40 seconds
> with `git verify-commit $(git rev-list HEAD)`. This is what the pre-push
> hook does now.
> Checking the commits one at a time takes ~105 seconds, using something
> like this:
> for commit in $(git rev-list HEAD); do
> if ! git verify-commit $commit; then
> echo $commit
> We could make the hook do something like that. Thoughts? I think the
> performance regression is worth the convenience of knowing why it
For the pre-push hook, the overhead seems reasonable (perhaps we could
limit the range to commits after the first signed commit to avoid
looping for no reason?) and an improvement.
Eventually we could rewrite in Scheme using guile-git, which should be
faster (no need to fork that much).