Re: Mention that .sig files are handled automatically

[John Darrington]

I agree.  I will change "may not" to "should not", and commit.

J'

On Wed, Sep 20, 2017 at 01:34:53PM -0400, Paul Smith wrote:
     On Wed, 2017-09-20 at 19:24 +0200, John Darrington wrote:
     > The text you proposed confused me when I read it without the context of 
your email.
     > I propose slightly different wording:
     > 
     >  The .sig file may not be explicitly mentioned in a directive.   When 
you 
     >  specify a directive to operate on a file, its corresponding .sig file 
will
     >  be handled automatically.
     > 
     > What do you think?
     
     I don't like using "may not" here because it's ambiguous: depending on
     how the reader interprets it, it might mean that you could if you wanted
     to, but don't have to.  I think this should be "should not" to make
     clear that you shouldn't do it at all.
     
     Otherwise it's OK with em.
     
     On Sun, Dec 11, 2016 at 10:31:48AM -0500, Paul Smith wrote:
          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
          ??allowed.
          ??
          +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

-- 
Avoid eavesdropping.  Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.

signature.asc
Description: Digital signature