[Top][All Lists]

[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: Sat, 12 Dec 2009 16:48:10 +0000

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       09/12/12 16:48:10

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        better upload examples, from ward


Index: ChangeLog
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -b -r1.102 -r1.103
--- ChangeLog   12 Dec 2009 00:07:06 -0000      1.102
+++ ChangeLog   12 Dec 2009 16:48:10 -0000      1.103
@@ -1,7 +1,13 @@
+2009-12-12  Karl Berry  <address@hidden>
+       * maintain.texi (Automated Upload Procedure): try to be more
+       explicit about the example gpg commands, etc.
+       Suggestion from Ward Vandewege.
 2009-12-11  Ralf Wildenhues  <address@hidden>
        Do not recommend world-writable directories in package tarballs.
-       * doc/standards.texi (Releases): Change recommended directory
+       * standards.texi (Releases): change recommended directory
        mode to 755, include justification and refer to original text;
        following CVE-2009-4029.
        Report by Jim Meyering.

Index: maintain.texi
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.176
retrieving revision 1.177
diff -u -b -r1.176 -r1.177
--- maintain.texi       20 Nov 2009 17:45:11 -0000      1.176
+++ maintain.texi       12 Dec 2009 16:48:10 -0000      1.177
@@ -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 November 20, 2009
address@hidden lastupdate December 12, 2009
 @c %**end of header
 @dircategory GNU organization
@@ -1311,15 +1311,19 @@
-The file to be distributed (for example, @file{foo.tar.gz}).
+The file to be distributed; for example, @file{foo.tar.gz}.
-Detached GPG binary signature for (1), made using @samp{gpg -b}
-(for example, @file{foo.tar.gz.sig}).
+Detached GPG binary signature file for (1); for example,
address@hidden  Make this with @samp{gpg -b foo.tar.gz}.
-A clearsigned @dfn{directive file}, made using @samp{gpg --clearsign}
-(for example, @file{foo.tar.gz.directive.asc}).
+A clearsigned @dfn{directive file}; for example,
address@hidden  Make this by preparing the plain
+text file @file{foo.tar.gz.directive} and then run @samp{gpg
+--clearsign foo.tar.gz.directive}.  @xref{FTP Upload Directive File -
+v1.1}, for the contents of the directive file.
 @end enumerate
 The names of the files are important. The signature file must have the
@@ -1351,8 +1355,8 @@
 package. You also receive a message when your upload has been successfully
-One relatively easy way to create and transfer the necessary files is
-to use the @code{gnupload} script, which is available from the
+One automated way to create and transfer the necessary files is to use
+the @code{gnupload} script, which is available from the
 @file{build-aux/} directory of the @code{gnulib} project at
 @url{}.  @code{gnupload} can
 also remove uploaded files.  Run @code{gnupload --help} for a
@@ -1361,10 +1365,10 @@
 @code{gnupload} uses the @code{ncftpput} program to do the actual
 transfers; if you don't happen to have the @code{ncftp} package
 installed, the @code{ncftpput-ftp} script in the @file{build-aux/}
-directory of @code{gnulib}.  serves as a replacement which uses plain
+directory of @code{gnulib} serves as a replacement which uses plain
 command line @code{ftp}.
-If you have difficulties processing an upload, email
+If you have difficulties with an upload, email

reply via email to

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