[git] GnuPG - branch, master, updated. gnupg-2.1.9-201-gfdd2cc5
by Werner Koch
cvs at cvs.gnupg.org
Mon Nov 30 16:10:00 CET 2015
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 fdd2cc5f3b257bac056992b79623310bb0b494d4 (commit)
from b2b079cb2f06067012e311434000d1cb5d6de8a2 (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 fdd2cc5f3b257bac056992b79623310bb0b494d4
Author: Werner Koch <wk at gnupg.org>
Date: Mon Nov 30 16:01:07 2015 +0100
doc: Clarify dirmngr's --keyserver option.
--
GnuPG-bug-id: 2165
diff --git a/doc/dirmngr.texi b/doc/dirmngr.texi
index e453e8a..6a4d6d6 100644
--- a/doc/dirmngr.texi
+++ b/doc/dirmngr.texi
@@ -255,8 +255,8 @@ keyservers, or "mailto" for the Graff email keyserver. Note that your
particular installation of GnuPG may have other keyserver types
available as well. Keyserver schemes are case-insensitive. After the
keyserver name, optional keyserver configuration options may be
-provided. These are the same as the global @option{--keyserver-options}
-from below, but apply only to this particular keyserver.
+provided. These are the same as the @option{--keyserver-options} of
+ at command{gpg}, but apply only to this particular keyserver.
Most keyservers synchronize with each other, so there is generally no
need to send keys to more than one server. The keyserver
-----------------------------------------------------------------------
Summary of changes:
doc/dirmngr.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
hooks/post-receive
--
The GNU Privacy Guard
http://git.gnupg.org
More information about the Gnupg-commits
mailing list