gnustandards-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnustandards ChangeLog maintain.texi


From: Karl Berry
Subject: gnustandards ChangeLog maintain.texi
Date: Fri, 15 Jun 2012 15:56:26 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       12/06/15 15:56:26

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        confirm gpg --gen-key answers

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.164&r2=1.165
http://cvs.savannah.gnu.org/viewcvs/gnustandards/maintain.texi?cvsroot=gnustandards&r1=1.223&r2=1.224

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.164
retrieving revision 1.165
diff -u -b -r1.164 -r1.165
--- ChangeLog   1 Jun 2012 17:15:42 -0000       1.164
+++ ChangeLog   15 Jun 2012 15:56:26 -0000      1.165
@@ -1,3 +1,8 @@
+2012-06-15  Karl Berry  <address@hidden>
+
+       * maintain.texi (Automated Upload Registration): must confirm
+       some of the answers to gpg --gen-key, not just accept.
+
 2012-06-01  Thien-Thi Nguyen  <address@hidden>
        and Karl Berry  <address@hidden>
 

Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.223
retrieving revision 1.224
diff -u -b -r1.223 -r1.224
--- maintain.texi       21 May 2012 00:38:10 -0000      1.223
+++ maintain.texi       15 Jun 2012 15:56:26 -0000      1.224
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
address@hidden lastupdate May 20, 2012
address@hidden lastupdate June 12, 2012
 @c %**end of header
 
 @dircategory GNU organization
@@ -1521,7 +1521,7 @@
 In the @samp{My Account Conf} page on @code{savannah}, upload the GPG
 key you will use to sign your packages.  If you haven't created one
 before, you can do so with the command @code{gpg --gen-key} (you can
-accept all the default answers to its questions).
+accept and/or confirm the default answers to its questions).
 
 Optional but recommended: Send your key to a GPG public key server:
 @code{gpg --keyserver keys.gnupg.net --send-keys @var{keyid}}, where



reply via email to

[Prev in Thread] Current Thread [Next in Thread]