gnustandards ChangeLog maintain.texi

[Karl Berry]

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Karl Berry <karl>       08/11/14 19:10:27

Modified files:
        .              : ChangeLog maintain.texi 

Log message:
        gnupload can --delete too

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/ChangeLog?cvsroot=gnustandards&r1=1.85&r2=1.86
http://cvs.savannah.gnu.org/viewcvs/gnustandards/maintain.texi?cvsroot=gnustandards&r1=1.166&r2=1.167

Patches:
Index: ChangeLog
===================================================================
RCS file: /sources/gnustandards/gnustandards/ChangeLog,v
retrieving revision 1.85
retrieving revision 1.86
diff -u -b -r1.85 -r1.86
--- ChangeLog   10 Nov 2008 23:10:10 -0000      1.85
+++ ChangeLog   14 Nov 2008 19:10:27 -0000      1.86
@@ -1,3 +1,8 @@
+2008-11-14  Karl Berry  <address@hidden>
+
+       * maintain.texi (Automated Upload Procedure): mention that
+       gnupload can now delete files as well as upload them.
+
 2008-11-10  Karl Berry  <address@hidden>
 
        * fdl.texi: update to 1.3 file.  Missed this earlier.

Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.166
retrieving revision 1.167
diff -u -b -r1.166 -r1.167
--- maintain.texi       10 Nov 2008 23:10:16 -0000      1.166
+++ maintain.texi       14 Nov 2008 19:10:27 -0000      1.167
@@ -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 8, 2008
address@hidden lastupdate November 14, 2008
 @c %**end of header
 
 @dircategory GNU organization
@@ -1261,9 +1261,9 @@
 
 @cindex uploads
 
-Once you have registered your information as described in the
-previous section, you will be able to do unattended ftp uploads using
-the following procedure.
+Once you have registered your information as described in the previous
+section, you will be able to do ftp uploads for yourself using the
+following procedure.
 
 For each upload destined for @code{ftp.gnu.org} or
 @code{alpha.gnu.org}, three files (a @dfn{triplet}) need to be
@@ -1290,9 +1290,9 @@
 @emph{will not be processed}.
 
 Since v1.1 of the upload script, it is also possible to upload a
address@hidden file} on its own to perform certain operations on
-uploaded files.  @xref{FTP Upload Directive File - v1.1}, for more
-information.
+clearsigned directive file on its own (no accompanying @file{.sig} or
+any other file) to perform certain operations on the server.
address@hidden Upload Directive File - v1.1}, for more information.
 
 Upload the file(s) via anonymous ftp to @code{ftp-upload.gnu.org}. If
 the upload is destined for @code{ftp.gnu.org}, place the file(s) in
@@ -1314,14 +1314,15 @@
 One relatively easy 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
address@hidden://savannah.gnu.org/projects/gnulib}.  Run @code{gnupload
---help} for a description and examples.
address@hidden://savannah.gnu.org/projects/gnulib}.  @code{gnupload} can
+also remove uploaded files.  Run @code{gnupload --help} for a
+description and examples.
 
 @code{gnupload} uses the @code{ncftpput} program to do the actual
 transfers; if you don't happen to have the @code{ncftp} package
-installed, you can use the @code{ncftpput-ftp} script as a
-replacement, which uses plain command line @code{ftp}.  It's also
-available from the @file{build-aux/} directory of @code{gnulib}.
+installed, the @code{ncftpput-ftp} script in the @file{build-aux/}
+directory of @code{gnulib}.  serves as a replacement which uses plain
+command line @code{ftp}.
 
 If you have difficulties processing an upload, email
 @email{ftp-upload@@gnu.org}.
@@ -1376,7 +1377,7 @@
 of the directives @code{symlink}, @code{rmsymlink} or @code{archive},
 in addition to the obligatory @code{directory} and @code{version}
 directives.  A @code{filename} directive is not allowed, and a
address@hidden directive is optional.
address@hidden directive remains optional.
 
 If you use more than one directive, the directives are executed in the
 sequence they are specified in.