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

* HACKING (Release Procedure): Here.

diff --git a/ChangeLog b/ChangeLog
index a1581fd8d3820de8534f71f14c85744c0b03a3d8..5eb84a0242e50f5b65d864b5b2eddc65081660ea 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-01-28  Akim Demaille  <demaille@gostai.com>
 
        * NEWS: Update information about 2.4.1 and 2.4.2.

diff --git a/HACKING b/HACKING
index 091ba66cfc63080d70097f9c8d733933f2ad18a9..10cac90a188b40c8f926adba151353cfb1eeb2e6 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -145,9 +145,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