security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2024-12-21 10:09:57 +01:00
Code Activity

doc: Revert the bug reporting address to bugs.gnupg.org

Browse Source 
--

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@gnupg.org>
This commit is contained in:
Werner Koch 2017-07-24 10:41:30 +02:00
parent 45e40487fb
commit 5dac85fba7
No known key found for this signature in database
GPG Key ID: E3FDFF218E45B72B
6 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
AUTHORS
View File

@ -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@gnupg.org>
Maintainer: Werner Koch <wk@gnupg.org>
License: GPLv3+

2
README
View File

@ -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@gnupg.org>.
Please direct questions about GnuPG to the users mailing list or one

2
configure.ac
View File

@ -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

2
doc/announce-2.1.txt
View File

@ -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

2
doc/faq.org
View File

@ -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:

2
doc/gpg.texi
View File

@ -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 *************** **************