From: Leo Famulari <leo@famulari.name>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: Bad signature on commit 6a34f4ccc8a5d (gnu: python-prompt-toolkit: Update to 1.0.9.)
Date: Thu, 29 Dec 2016 02:38:09 -0500 [thread overview]
Message-ID: <20161229073809.GA32137@jasmine> (raw)
In-Reply-To: <20161229064459.GA27432@jasmine>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Thu, Dec 29, 2016 at 01:44:59AM -0500, Leo Famulari wrote:
> 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.
The hook will only apply when pushing to Savannah if you put this test
at the beginning of the hook:
case "$2" in
*git.sv.gnu.org*)
break
;;
*)
exit 0
;;
esac
Commit signatures will be verified before pushing to Savannah, but it
doesn't interfere when pushing to another repository. I think this is
right balance between safety and convenience.
If people think the hook is correct, we could recommend it in HACKING.
> #!/gnu/store/b1yqjimbdh5bf9jnizd4h7yf110744j2-bash-4.3.42/bin/sh
Oops! It should all work with #!/bin/sh.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2016-12-29 7:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 2:10 Bad signature on commit 6a34f4ccc8a5d (gnu: python-prompt-toolkit: Update to 1.0.9.) Leo Famulari
2016-12-29 2:47 ` Leo Famulari
2016-12-29 3:04 ` Tobias Geerinckx-Rice
2016-12-29 17:13 ` Leo Famulari
2016-12-29 2:49 ` Tobias Geerinckx-Rice
2016-12-29 6:08 ` John Darrington
2016-12-29 6:39 ` Leo Famulari
2016-12-29 6:44 ` Leo Famulari
2016-12-29 7:38 ` Leo Famulari [this message]
2017-01-02 20:59 ` Ludovic Courtès
2017-01-03 6:24 ` Leo Famulari
2017-01-03 12:34 ` Ludovic Courtès
2017-01-03 17:29 ` Leo Famulari
2017-01-04 21:05 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161229073809.GA32137@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.