From 20e29643449adbb9658c0d3bec9c8b117697fe41 Mon Sep 17 00:00:00 2001 From: Ludovic Courtès Date: Sat, 23 Jul 2016 12:48:51 +0200 Subject: doc: Explain how to set up Git for signing. * HACKING (Commit Access): Give instructions on how to set up Git for signing. --- HACKING | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) (limited to 'HACKING') diff --git a/HACKING b/HACKING index d5828f6836..28948b3e23 100644 --- a/HACKING +++ b/HACKING @@ -2,7 +2,7 @@ #+TITLE: Hacking GNU Guix and Its Incredible Distro -Copyright © 2012, 2013, 2014 Ludovic Courtès +Copyright © 2012, 2013, 2014, 2016 Ludovic Courtès Copyright © 2015 Mathieu Lirzin Copying and distribution of this file, with or without modification, @@ -35,9 +35,13 @@ upgrading GnuTLS or GLib.) We have a mailing list for commit notifications (guix-commits@gnu.org), so people can notice. Before pushing your changes, make sure to run ‘git pull --rebase’. -All commits that are pushed to the central repository on Savannah should be -signed with a PGP key, and the public key should be uploaded to your user -account on Savannah. +All commits that are pushed to the central repository on Savannah must be +signed with an OpenPGP key, and the public key should be uploaded to your user +account on Savannah and to public key servers, such as ‘pgp.mit.edu’. To +configure Git to automatically sign commits, run: + + git config commit.gpgsign true + git config user.signingkey CABBA6EA1DC0FF33 For anything else, please post to guix-devel@gnu.org and leave time for a review, without committing anything. If you didn’t receive any reply -- cgit 1.4.1