[git] GnuPG - branch, master, updated. gnupg-2.1.21-138-g5dac85f

[by Werner Koch]

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  5dac85fba78075b525a9aab24ea079fc4addf372 (commit)
      from  45e40487fb7bb51228c96c8966e38c643a9b9ba5 (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 5dac85fba78075b525a9aab24ea079fc4addf372
Author: Werner Koch <wk at gnupg.org>
Date:   Mon Jul 24 10:41:30 2017 +0200

    doc: Revert the bug reporting address to bugs.gnupg.org
    
    --
    
    dev.gnupg org is the development platform but the canonical bug
    address is and has always been bugs.gnupg.org.  We should keep on
    using this address for the case that we switch the tracker again or
    split it off the development system.
    
    That is also the reason why we should keep on communicating a plain
    bug number without the 'T' prefix.
    
    Signed-off-by: Werner Koch <wk at gnupg.org>

diff --git a/AUTHORS b/AUTHORS
index 76eb6e4..99bb0e2 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -2,7 +2,7 @@ Program: GnuPG
 Homepage: https://www.gnupg.org
 Download: https://gnupg.org/ftp/gcrypt/gnupg/
 Repository: git://git.gnupg.org/gnupg.git
-Bug reports: https://dev.gnupg.org
+Bug reports: https://bugs.gnupg.org
 Security related bug reports: <security at gnupg.org>
 Maintainer: Werner Koch <wk at gnupg.org>
 License: GPLv3+
diff --git a/README b/README
index e0c5d71..aaf347c 100644
--- a/README
+++ b/README
@@ -227,7 +227,7 @@
   https://www.gnupg.org/documentation/mailing-lists.html for archives
   of the mailing lists.
 
-  Please direct bug reports to http://dev.gnupg.org or post them
+  Please direct bug reports to [[http://bugs.gnupg.org]] or post them
   direct to the mailing list <gnupg-devel at gnupg.org>.
 
   Please direct questions about GnuPG to the users mailing list or one
diff --git a/configure.ac b/configure.ac
index 56cb78e..02ee1a2 100644
--- a/configure.ac
+++ b/configure.ac
@@ -47,7 +47,7 @@ m4_define([mym4_version],      m4_argn(4, mym4_verslist))
 m4_define([mym4_revision],     m4_argn(7, mym4_verslist))
 m4_define([mym4_revision_dec], m4_argn(8, mym4_verslist))
 m4_esyscmd([echo ]mym4_version[>VERSION])
-AC_INIT([mym4_package],[mym4_version], [https://dev.gnupg.org])
+AC_INIT([mym4_package],[mym4_version], [https://bugs.gnupg.org])
 
 NEED_GPG_ERROR_VERSION=1.24
 
diff --git a/doc/announce-2.1.txt b/doc/announce-2.1.txt
index 137f0b1..eccd0e7 100644
--- a/doc/announce-2.1.txt
+++ b/doc/announce-2.1.txt
@@ -236,7 +236,7 @@ Support
 Please consult the archive of the gnupg-users mailing list before
 reporting a bug <https://gnupg.org/documentation/mailing-lists.html>.
 We suggest to send bug reports for a new release to this list in favor
-of filing a bug at <https://dev.gnupg.org>.  For commercial support
+of filing a bug at <https://bugs.gnupg.org>.  For commercial support
 requests we keep a list of known service companies at:
 
   https://gnupg.org/service.html
diff --git a/doc/faq.org b/doc/faq.org
index 5619faa..ddbeafa 100644
--- a/doc/faq.org
+++ b/doc/faq.org
@@ -1139,7 +1139,7 @@ update this FAQ in the next month.  See the section "Changes" for recent updates
     the list of reported bugs on the documentation page). If you're
     not sure about it being a bug, you can send mail to the
     gnupg-devel list. Otherwise, use the bug tracking system at
-    [[https://dev.gnupg.org][dev.gnupg.org]].
+    [[https://bugs.gnupg.org][bugs.gnupg.org]].
 
 ** Why doesn't GnuPG support X.509 certificates?
    :PROPERTIES:
diff --git a/doc/gpg.texi b/doc/gpg.texi
index 1b5dee0..9147bdf 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -3806,7 +3806,7 @@ may be recoverable from it later.
 
 Before you report a bug you should first search the mailing list
 archives for similar problems and second check whether such a bug has
-already been reported to our bug tracker at https://dev.gnupg.org .
+already been reported to our bug tracker at @url{https://bugs.gnupg.org}.
 
 @c *******************************************
 @c ***************              **************

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

Summary of changes:
 AUTHORS              | 2 +-
 README               | 2 +-
 configure.ac         | 2 +-
 doc/announce-2.1.txt | 2 +-
 doc/faq.org          | 2 +-
 doc/gpg.texi         | 2 +-
 6 files changed, 6 insertions(+), 6 deletions(-)


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