[git] GnuPG - branch, master, updated. gnupg-2.1.15-126-g55675fa

[by Daniel Kahn Gillmor]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The GNU Privacy Guard".

The branch, master has been updated
       via  55675fa5a03969a896c8a7b19af22a2fd91d9747 (commit)
      from  7305d27f36148a7fb8c2f4ef5b94774cbd21b18e (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 55675fa5a03969a896c8a7b19af22a2fd91d9747
Author: Daniel Kahn Gillmor <dkg at fifthhorseman.net>
Date:   Sat Sep 17 11:34:35 2016 -0400

    doc: Clarify forward-compatible expectations
    
    --
    Encourage better parsers/interpreters of with-colons
    and status-fd output.
    
    Signed-off-by: Daniel Kahn Gillmor <dkg at fifthhorseman.net>

diff --git a/doc/DETAILS b/doc/DETAILS
index 1411c71..a264e53 100644
--- a/doc/DETAILS
+++ b/doc/DETAILS
@@ -36,7 +36,9 @@ Note that new version of GnuPG or the use of certain options may add
 new fields to the output.  Parsers should not assume a limit on the
 number of fields per line.  Some fields are not yet used or only used
 with certain record types; parsers should ignore fields they are not
-aware of.
+aware of.  New versions of GnuPG or the use of certain options may add
+new types of records as well.  Parsers should ignore any record whose
+type they do not recognize for forward-compatibility.
 
 The double =--with-fingerprint= prints the fingerprint for the subkeys
 too.  Old versions of gpg used a slightly different format and required
@@ -358,8 +360,10 @@ pkd:0:1024:B665B1435F4C2 .... FF26ABB:
 
   Every line is prefixed with "[GNUPG:] ", followed by a keyword with
   the type of the status line and some arguments depending on the type
-  (maybe none); an application should always be prepared to see new
-  keyworkds or more arguments in future versions.
+  (maybe none); an application should always be willing to ignore
+  unknown keywords that may be emitted by future versions of GnuPG.
+  Also, new versions of GnuPG may add arguments to existing keywords.
+  Any additional arguments should be ignored for forward-compatibility.
 
 ** General status codes
 *** NEWSIG [<signers_uid>]

-----------------------------------------------------------------------

Summary of changes:
 doc/DETAILS | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
The GNU Privacy Guard
http://git.gnupg.org