Add reminder about uploading public key to keys.gnupg.net.

* HACKING (Release Procedure): Here.
(cherry picked from commit 06c3084fb5a566e802ba35a9cc54be51db7fe6f1)

diff --git a/ChangeLog b/ChangeLog
index 0eae269faec3525d9a97774a435979066937d88b..92166b09c08a96e2bae8a826d3a0738193cadc06 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2009-02-03  Joel E. Denny  <jdenny@ces.clemson.edu>
+
+       Add reminder about uploading public key to keys.gnupg.net.
+       * HACKING (Release Procedure): Here.
+
 2009-03-31  Akim Demaille  <demaille@gostai.com>
 
        bootstrap: --help to stdout.

diff --git a/HACKING b/HACKING
index 1469396597bbdb0ca07e1eec9bc2bc30d3c26be3..16dff1a59a35d84b4e6bf4d8c53c9df9d4d66e8d 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -257,9 +257,15 @@ The generic GNU upload procedure is at:
 
   http://www.gnu.org/prep/maintain/maintain.html#Automated-FTP-Uploads
 
-After following the instructions there to register your information so you're
-permitted to upload, here's a brief reminder of how to roll the tarballs and
-upload them:
+Follow the instructions there to register your information so you're permitted
+to upload.  Make sure your public key has been uploaded at least to
+keys.gnupg.net.  You can upload it with:
+
+  gpg --keyserver keys.gnupg.net --send-keys F125BDF3
+
+where F125BDF3 should be replaced with your key ID.
+
+Here's a brief reminder of how to roll the tarballs and upload them:
 
 *** make distcheck
 *** gpg -b bison-2.3b.tar.gz