From: Leo Famulari <leo@famulari.name>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Updating the “pre-push” Git hook
Date: Tue, 26 May 2020 12:41:47 -0400 [thread overview]
Message-ID: <20200526164147.GB21828@jasmine.lan> (raw)
In-Reply-To: <87pnar22oz.fsf@yucca>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
On Mon, May 25, 2020 at 01:13:16PM -0700, Vagrant Cascadian wrote:
> Wait a minute... you're saying this is something that needs to be
> configured on each committer's machine(s)?
Yes, it was recommended in HACKING and then, after we removed that file,
in the Commit Access section of the manual. We try to remind new
committers to read these files but maybe we forgot for you.
However, the security model does not depend on either it or on a
post-receive server hook. It's simply to prevent mistakes.
There are commits in the repo that are unsigned when they should have
been signed, and even one commit that is signed but that fails the
signature check :/
A simple pre-push hook would have caught that.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-26 16:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 20:44 Updating the “pre-push” Git hook Ludovic Courtès
2020-05-22 21:17 ` Leo Famulari
2020-05-24 7:27 ` Ricardo Wurmus
2020-05-24 21:44 ` Ludovic Courtès
2020-05-25 9:50 ` Ricardo Wurmus
2020-05-25 22:04 ` Ludovic Courtès
2020-05-24 6:41 ` Efraim Flashner
2020-05-24 21:45 ` Ludovic Courtès
2020-05-25 5:50 ` Efraim Flashner
2020-05-25 21:31 ` Ludovic Courtès
2020-05-25 20:13 ` Vagrant Cascadian
2020-05-25 21:37 ` Ludovic Courtès
2020-05-26 16:41 ` Leo Famulari [this message]
2020-05-29 16:45 ` Heads-up: “pre-push” Git hook updated Ludovic Courtès
2020-05-29 17:07 ` Pierre Neidhardt
2020-05-29 18:39 ` Christopher Baines
2020-06-04 11:50 ` Ludovic Courtès
2020-06-04 18:33 ` Christopher Baines
2020-06-08 18:41 ` Vagrant Cascadian
2020-06-09 15:46 ` 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=20200526164147.GB21828@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.org \
/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).