Re: [PATCH 2/2] bugzilla: remove `gcc-bugs@` mailing list address

[Xi Ruoyao]

On Wed, 2023-11-22 at 20:57 -0500, Ben Boeckel wrote:
> Is there a version of autoconf I should use? I have 2.71 laying around
> but see that these were generated with 2.69. If you want me to regen
> with 2.71, I'll do that as separate prep commits so that this diff is
> sensible. Or I can try and dig up a 2.69 in some container to do it.

Use 2.69.

A container is not needed, you can just install autoconf-2.69 with --
prefix=$HOME/ac269 (or another directory you like) and run
$HOME/ac269/bin/autoconf, $HOME/ac269/bin/autoheader, etc.

-- 
Xi Ruoyao 
School of Aerospace Science and Technology, Xidian University

Re: [PATCH 2/2] bugzilla: remove `gcc-bugs@` mailing list address

[Ben Boeckel]

On Wed, Nov 22, 2023 at 23:15:56 +, Joseph Myers wrote:
> On Mon, 20 Nov 2023, Ben Boeckel wrote:
> 
> > Bugzilla is preferred today.
> > 
> > ChangeLog:
> > 
> > * config-ml.in: Replace gcc-bugs@ with Bugzilla link.
> > * symlink-tree: Replace gcc-bugs@ with Bugzilla link.
> 
> I don't think we should use a URL that redirects (i.e. 
> https://gcc.gnu.org/bugzilla should preferably have a trailing '/'), and 
> arguably we should use https://gcc.gnu.org/bugs/ as the URL; that's the 
> preferred one to point people to for bugs in the compilers themselves, 
> since it gives more instructions on bug reporting (though those 
> instructions may be less relevant for bugs in these files).

I'll update the URL.

> codingconventions.html claims that symlink-tree is "copied from mainline 
> automake".  That is, I think, out-of-date information: automake's 
> contrib/multilib/README says "The master (and probably more up-to-date) 
> copies of the 'config-ml.in' and 'symlink-tree' files are maintained in 
> the GCC development tree".  But it does indicate that 
> codingconventions.html itself should be updated to stop suggesting 
> symlink-tree is maintained elsewhere.

I'll also change that.

> > libcpp/ChangeLog:
> > 
> > * configure: Replace gcc-bugs@ with Bugzilla link.
> > * configure.ac: Replace gcc-bugs@ with Bugzilla link.
> > 
> > libdecnumber/ChangeLog:
> > 
> > * configure: Replace gcc-bugs@ with Bugzilla link.
> > * configure.ac: Replace gcc-bugs@ with Bugzilla link.
> 
> I hope the configure changes are the same as you get with regeneration 
> with the right autoconf version, and so should be described as 
> regeneration in the ChangeLog entries.

Is there a version of autoconf I should use? I have 2.71 laying around
but see that these were generated with 2.69. If you want me to regen
with 2.71, I'll do that as separate prep commits so that this diff is
sensible. Or I can try and dig up a 2.69 in some container to do it.

Thanks,

--Ben

Re: [PATCH 2/2] bugzilla: remove `gcc-bugs@` mailing list address

[Joseph Myers]

On Mon, 20 Nov 2023, Ben Boeckel wrote:

> Bugzilla is preferred today.
> 
> ChangeLog:
> 
>   * config-ml.in: Replace gcc-bugs@ with Bugzilla link.
>   * symlink-tree: Replace gcc-bugs@ with Bugzilla link.

I don't think we should use a URL that redirects (i.e. 
https://gcc.gnu.org/bugzilla should preferably have a trailing '/'), and 
arguably we should use https://gcc.gnu.org/bugs/ as the URL; that's the 
preferred one to point people to for bugs in the compilers themselves, 
since it gives more instructions on bug reporting (though those 
instructions may be less relevant for bugs in these files).

codingconventions.html claims that symlink-tree is "copied from mainline 
automake".  That is, I think, out-of-date information: automake's 
contrib/multilib/README says "The master (and probably more up-to-date) 
copies of the 'config-ml.in' and 'symlink-tree' files are maintained in 
the GCC development tree".  But it does indicate that 
codingconventions.html itself should be updated to stop suggesting 
symlink-tree is maintained elsewhere.

> libcpp/ChangeLog:
> 
>   * configure: Replace gcc-bugs@ with Bugzilla link.
>   * configure.ac: Replace gcc-bugs@ with Bugzilla link.
> 
> libdecnumber/ChangeLog:
> 
>   * configure: Replace gcc-bugs@ with Bugzilla link.
>   * configure.ac: Replace gcc-bugs@ with Bugzilla link.

I hope the configure changes are the same as you get with regeneration 
with the right autoconf version, and so should be described as 
regeneration in the ChangeLog entries.

-- 
Joseph S. Myers
jos...@codesourcery.com

[PATCH 2/2] bugzilla: remove `gcc-bugs@` mailing list address

[Ben Boeckel]

Bugzilla is preferred today.

ChangeLog:

* config-ml.in: Replace gcc-bugs@ with Bugzilla link.
* symlink-tree: Replace gcc-bugs@ with Bugzilla link.

fixincludes/ChangeLog:

* README: Replace gcc-bugs@ with Bugzilla link.

gcc/testsuite/ChangeLog:

* lib/file-format.exp: Replace gcc-bugs@ with Bugzilla link.

libcpp/ChangeLog:

* configure: Replace gcc-bugs@ with Bugzilla link.
* configure.ac: Replace gcc-bugs@ with Bugzilla link.

libdecnumber/ChangeLog:

* configure: Replace gcc-bugs@ with Bugzilla link.
* configure.ac: Replace gcc-bugs@ with Bugzilla link.

Signed-off-by: Ben Boeckel 
---
 config-ml.in  |  2 +-
 fixincludes/README|  4 ++--
 gcc/testsuite/lib/file-format.exp |  4 ++--
 libcpp/configure  | 12 ++--
 libcpp/configure.ac   |  2 +-
 libdecnumber/configure| 12 ++--
 libdecnumber/configure.ac |  2 +-
 symlink-tree  |  2 +-
 8 files changed, 20 insertions(+), 20 deletions(-)

diff --git a/config-ml.in b/config-ml.in
index 6aff74410c0..8724cf6370e 100644
--- a/config-ml.in
+++ b/config-ml.in
@@ -24,7 +24,7 @@
 # configuration script generated by Autoconf, you may include it under
 # the same distribution terms that you use for the rest of that program.
 #
-# Please report bugs to 
+# Please report bugs to 
 # and send patches to .
 
 # It is advisable to support a few --enable/--disable options to let the
diff --git a/fixincludes/README b/fixincludes/README
index 98480165d10..74eb8373224 100644
--- a/fixincludes/README
+++ b/fixincludes/README
@@ -6,8 +6,8 @@ If you are having some problem with a system header that is 
either
 broken by the manufacturer, or is broken by the fixinclude process,
 then you will need to alter or add information to the include fix
 definitions file, ``inclhack.def''.  Please also send relevant
-information to gcc-b...@gcc.gnu.org, gcc-patches@gcc.gnu.org and,
-please, to me:  bk...@gnu.org.
+information to https://gcc.gnu.org/bugzilla, gcc-patches@gcc.gnu.org
+and, please, to me:  bk...@gnu.org.
 
 To make your fix, you will need to do several things:
 
diff --git a/gcc/testsuite/lib/file-format.exp 
b/gcc/testsuite/lib/file-format.exp
index 9bf89e2814c..3bfdc4f8264 100644
--- a/gcc/testsuite/lib/file-format.exp
+++ b/gcc/testsuite/lib/file-format.exp
@@ -14,8 +14,8 @@
 # along with GCC; see the file COPYING3.  If not see
 # .
 
-# Please email any bugs, comments, and/or additions to this file to:
-# gcc-b...@gcc.gnu.org
+# Please report any bugs, comments, and/or additions to this file to:
+# https://gcc.gnu.org/bugzilla
 
 # This file defines a proc for determining the file format in use by the
 # target.  This is useful for tests that are only supported by certain file
diff --git a/libcpp/configure b/libcpp/configure
index ed98f40a1c1..bdfd83a1973 100755
--- a/libcpp/configure
+++ b/libcpp/configure
@@ -2,7 +2,7 @@
 # Guess values for system-dependent variables and create Makefiles.
 # Generated by GNU Autoconf 2.69 for cpplib  .
 #
-# Report bugs to .
+# Report bugs to .
 #
 #
 # Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
@@ -267,7 +267,7 @@ fi
 $as_echo "$0: be upgraded to zsh 4.3.4 or later."
   else
 $as_echo "$0: Please tell bug-autoc...@gnu.org and
-$0: gcc-b...@gcc.gnu.org about your system, including any
+$0: https://gcc.gnu.org/bugzilla about your system, including any
 $0: error possibly output before this message. Then install
 $0: a modern shell, or manually run the script under such a
 $0: shell if you do have one."
@@ -582,7 +582,7 @@ PACKAGE_NAME='cpplib'
 PACKAGE_TARNAME='cpplib'
 PACKAGE_VERSION=' '
 PACKAGE_STRING='cpplib  '
-PACKAGE_BUGREPORT='gcc-b...@gcc.gnu.org'
+PACKAGE_BUGREPORT='https://gcc.gnu.org/bugzilla'
 PACKAGE_URL=''
 
 ac_unique_file="ucnid.h"
@@ -1410,7 +1410,7 @@ Some influential environment variables:
 Use these variables to override the choices made by `configure' or to help
 it to find libraries and programs with nonstandard names/locations.
 
-Report bugs to .
+Report bugs to .
 _ACEOF
 ac_status=$?
 fi
@@ -1671,7 +1671,7 @@ $as_echo "$as_me: WARNING: $2: section \"Present But 
Cannot Be Compiled\"" >
 { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the 
compiler's result" >&5
 $as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;}
 ( $as_echo "## --- ##
-## Report this to gcc-b...@gcc.gnu.org ##
+## Report this to https://gcc.gnu.org/bugzilla ##
 ## --- ##"
  ) | sed "s/^/$as_me: WARNING: /" >&2
 ;;
@@ -8504,7 +8504,7 @@ $config_headers
 Configuration commands:
 $config_commands
 
-Report bugs to ."
+Report bugs to ."
 
 _ACEOF
 cat >>$CONFIG