all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Cc: guix-sysadmin <guix-sysadmin@gnu.org>
Subject: Authenticating maintenance.git
Date: Thu, 06 May 2021 13:03:21 +0200	[thread overview]
Message-ID: <87tungf7k6.fsf@gnu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

Hello Guix!

I’ve added a ‘.guix-authorizations’ file in maintenance.git, at last!
We can now authenticate the repository we’ve checked out:

  guix git authenticate 8a7e10b447b574279a7016ae6ea15bc7bcd46253 \
    "3CE4 6455 8A84 FDC6 9DB4  0CFB 090B 1199 3D9A EBB5" --stats

It’s also possible to authenticate all changes made to the repo since
the first signed commit in July 2016 by running:

  guix git authenticate 7f59985566b384e31da7e6f1a36744e9edfba54f \
    "3CE4 6455 8A84 FDC6 9DB4  0CFB 090B 1199 3D9A EBB5" \
    --historical-authorizations=historical-authorizations

If you ran the first command above before, you might want to clear your
authentication cache with:

  rm -rf ~/.cache/guix/authentication/checkouts

Note that ‘.guix-authorizations’ is a subset of the one on the main Guix
repository, but we can add people as needed.  I invite committers to
install the pre-push hook as mentioned in README:

  https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/README

Happy hacking!

Ludo’.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]

             reply	other threads:[~2021-05-06 11:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 11:03 Ludovic Courtès [this message]
2021-05-06 21:26 ` Authenticating maintenance.git Leo Famulari
2021-06-16  7:20 ` Chris Marusich
2021-06-20 16:25   ` Ludovic Courtès
2021-06-23  0:46     ` Chris Marusich
2021-06-24  1:01       ` Chris Marusich
2021-06-25 12:26         ` Maxime Devos
2021-06-29 14:36           ` 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=87tungf7k6.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-sysadmin@gnu.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 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.