[Top][All Lists]

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

Mention that .sig files are handled automatically

From: Paul Smith
Subject: Mention that .sig files are handled automatically
Date: Sun, 11 Dec 2016 10:31:48 -0500

When using the extra directives for uploads to archive files, I included
the .sig files as things to be archived which led to an error.

I recommend a patch similar to below, to be clear that you only need to
include the file or directory name to be managed and not the .sig file:

cvs diff: Diffing .
Index: maintain.texi
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.257
diff -u -r1.257 maintain.texi
--- maintain.texi       21 Jul 2016 20:17:35 -0000      1.257
+++ maintain.texi       11 Dec 2016 15:28:19 -0000
@@ -5,7 +5,7 @@
address@hidden For double-sided printing, uncomment:
address@hidden @setchapternewpage odd
address@hidden This date is automagically updated when you save this file:
address@hidden lastupdate July 21, 2016
address@hidden lastupdate December 11, 2016
address@hidden %**end of header
address@hidden GNU organization
@@ -1882,6 +1882,10 @@
 directive remains optional, and the @code{filename} directive is not
+You should include only the name of the file or directory to be
+managed in these directives: the @file{.sig} companion signature files
+will be handled automatically for you.
 When uploaded by itself, the name of the directive file is not
 important.  But it must be still be signed, using @samp{gpg
 --clearsign}; the resulting @file{.asc} file is what should be

reply via email to

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