From: Leo Famulari <leo@famulari.name>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: pre-push signature hook error reporting [was Re: [PATCH v6] gnu: python-sphinx: Update to 1.4.8.]
Date: Tue, 17 Jan 2017 14:39:02 -0500 [thread overview]
Message-ID: <20170117193902.GB6560@jasmine> (raw)
In-Reply-To: <587E306E.7010407@crazy-compilers.com>
On Tue, Jan 17, 2017 at 03:55:42PM +0100, Hartmut Goebel wrote:
> Am 17.01.2017 um 04:14 schrieb Leo Famulari:
> > with `git verify-commit $(git rev-list HEAD)`. This is what the pre-push
>
> As far as I understand the example hook, it would be possible to do
> something like
>
> git verify-commit $(git rev-list $remote_sha..$local_sha)
>
> this would only verify the commits which are going to be pushed.
I'm sorry that I was unclear.
If you read the hook, you'll see that it does what you suggest. I chose
to check the entire history as a benchmark.
next prev parent reply other threads:[~2017-01-17 19:39 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 ` pre-push signature hook error reporting [was Re: [PATCH v6] gnu: python-sphinx: Update to 1.4.8.] Leo Famulari
2017-01-17 11:34 ` 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 [this message]
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=20170117193902.GB6560@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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).