From: Joel E. Denny Date: Tue, 3 Feb 2009 08:08:32 +0000 (-0500) Subject: Add reminder about uploading public key to keys.gnupg.net. X-Git-Tag: v2.4.1a~62 X-Git-Url: https://git.saurik.com/bison.git/commitdiff_plain/015e86a7b2224848f3f1f29d7bdbf8e31d8bee34?ds=inline 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 0eae269f..92166b09 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2009-02-03 Joel E. Denny + + Add reminder about uploading public key to keys.gnupg.net. + * HACKING (Release Procedure): Here. + 2009-03-31 Akim Demaille bootstrap: --help to stdout. diff --git a/HACKING b/HACKING index 14693965..16dff1a5 100644 --- 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