From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: pre-push signature hook error reporting [was Re: [PATCH v6] gnu: python-sphinx: Update to 1.4.8.]
Date: Mon, 16 Jan 2017 22:14:14 -0500 [thread overview]
Message-ID: <20170117031414.GB23513@jasmine> (raw)
In-Reply-To: <20170113152400.GA24322@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
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:
https://git.kernel.org/cgit/git/git.git/tree/builtin/verify-commit.c?h=v2.11.0
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
fi
done
We could make the hook do something like that. Thoughts? I think the
performance regression is worth the convenience of knowing why it
failed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-17 3:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 16:14 [PATCH v6] gnu: python-sphinx: Update to 1.4.8 Danny Milosavljevic
2017-01-05 16:40 ` Marius Bakke
[not found] ` <8760lj5eb6.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
[not found] ` <20170113152400.GA24322@jasmine>
2017-01-17 3:14 ` Leo Famulari [this message]
2017-01-17 11:34 ` pre-push signature hook error reporting [was Re: [PATCH v6] gnu: python-sphinx: Update to 1.4.8.] Danny Milosavljevic
2017-01-17 12:56 ` Hartmut Goebel
2017-01-17 19:44 ` Leo Famulari
2017-01-17 19:38 ` Leo Famulari
2017-01-17 14:55 ` Hartmut Goebel
2017-01-17 19:39 ` Leo Famulari
2017-01-20 14:05 ` Ludovic Courtès
2017-01-21 1:39 ` Leo Famulari
2017-02-06 15:39 ` pre-push signature hook error reporting Leo Famulari
2017-02-06 16:37 ` Marius Bakke
2017-02-07 13:15 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170117031414.GB23513@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).