diff options
author | Joseph Myers <jsm28@cam.ac.uk> | 2000-09-30 09:04:01 +0100 |
---|---|---|
committer | Joseph Myers <jsm28@gcc.gnu.org> | 2000-09-30 09:04:01 +0100 |
commit | 28e6b1c270316aa93f2f095d560d5926716b3e26 (patch) | |
tree | 74fd8158da2089e49106f91dc29276cfe7a4bc64 | |
parent | 1bacc64eb001d64da643e099c8f7d34b7e4ea910 (diff) | |
download | gcc-28e6b1c270316aa93f2f095d560d5926716b3e26.zip gcc-28e6b1c270316aa93f2f095d560d5926716b3e26.tar.gz gcc-28e6b1c270316aa93f2f095d560d5926716b3e26.tar.bz2 |
c-tree.texi, [...]: Consistently use @email for formatting email addresses.
* c-tree.texi, contrib.texi, gcc.texi, install.texi, invoke.texi:
Consistently use @email for formatting email addresses.
cp:
* gxxint.texi: Use @email for formatting email addresses.
From-SVN: r36676
-rw-r--r-- | gcc/ChangeLog | 5 | ||||
-rw-r--r-- | gcc/c-tree.texi | 2 | ||||
-rw-r--r-- | gcc/contrib.texi | 2 | ||||
-rw-r--r-- | gcc/cp/ChangeLog | 4 | ||||
-rw-r--r-- | gcc/cp/gxxint.texi | 2 | ||||
-rw-r--r-- | gcc/gcc.texi | 14 | ||||
-rw-r--r-- | gcc/install.texi | 6 | ||||
-rw-r--r-- | gcc/invoke.texi | 2 |
8 files changed, 23 insertions, 14 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 79733ff..51c42f2 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,8 @@ +2000-09-30 Joseph S. Myers <jsm28@cam.ac.uk> + + * c-tree.texi, contrib.texi, gcc.texi, install.texi, invoke.texi: + Consistently use @email for formatting email addresses. + 2000-09-29 Richard Henderson <rth@cygnus.com> * cse.c (notreg_cost): New argument outer. diff --git a/gcc/c-tree.texi b/gcc/c-tree.texi index ac5957a..d2f63a1 100644 --- a/gcc/c-tree.texi +++ b/gcc/c-tree.texi @@ -76,7 +76,7 @@ that you need to ask questions not easily answered by the functions and macros available here. If that situation occurs, it is quite likely that GCC already supports the functionality you desire, but that the interface is simply not documented here. In that case, you should ask -the GCC maintainers (via mail to @url{mailto:gcc@@gcc.gnu.org}) about +the GCC maintainers (via mail to @email{gcc@@gcc.gnu.org}) about documenting the functionality you require. Similarly, if you find yourself writing functions that do not deal directly with your back-end, but instead might be useful to other people using the GCC front-end, you diff --git a/gcc/contrib.texi b/gcc/contrib.texi index 8a1effe..333dbb1 100644 --- a/gcc/contrib.texi +++ b/gcc/contrib.texi @@ -1,7 +1,7 @@ The GCC project would like to thank its many contributors. Without them the project would not have been nearly as successful as it has been. Any omissions in this list are accidental. Feel free to contact -@code{law@@cygnus.com} if you have been left out +@email{law@@cygnus.com} if you have been left out or some of your contributions are not listed. Please keep this list in alphabetical order. diff --git a/gcc/cp/ChangeLog b/gcc/cp/ChangeLog index 3f963d5..ead72e2 100644 --- a/gcc/cp/ChangeLog +++ b/gcc/cp/ChangeLog @@ -1,3 +1,7 @@ +2000-09-30 Joseph S. Myers <jsm28@cam.ac.uk> + + * gxxint.texi: Use @email for formatting email addresses. + 2000-09-29 Gabriel Dos Reis <gdr@codesourcery.com> * error.c: Remove direct obstack manipulation. Replace with diff --git a/gcc/cp/gxxint.texi b/gcc/cp/gxxint.texi index 492b995..7ed9690 100644 --- a/gcc/cp/gxxint.texi +++ b/gcc/cp/gxxint.texi @@ -9,7 +9,7 @@ @chapter Internal Architecture of the Compiler This is meant to describe the C++ front-end for gcc in detail. -Questions and comments to Benjamin Kosnik @code{<bkoz@@cygnus.com>}. +Questions and comments to Benjamin Kosnik @email{bkoz@@cygnus.com}. @menu * Limitations of g++:: diff --git a/gcc/gcc.texi b/gcc/gcc.texi index 60de94d..e038d78 100644 --- a/gcc/gcc.texi +++ b/gcc/gcc.texi @@ -2230,9 +2230,9 @@ suggestions for improvement of GCC are welcome in any case. @cindex bug report mailing lists @kindex gcc-bugs@@gcc.gnu.org or bug-gcc@@gnu.org Send bug reports for the GNU Compiler Collection to -@samp{gcc-bugs@@gcc.gnu.org}. In accordance with the GNU-wide +@email{gcc-bugs@@gcc.gnu.org}. In accordance with the GNU-wide convention, in which bug reports for tool ``foo'' are sent -to @samp{bug-foo@@gnu.org}, the address @samp{bug-gcc@@gnu.org} +to @samp{bug-foo@@gnu.org}, the address @email{bug-gcc@@gnu.org} may also be used; it will forward to the address given above. Please read @uref{http://www.gnu.org/software/gcc/bugs.html} for @@ -2650,7 +2650,7 @@ The default is @samp{sw-bug}. If you would like to write bug fixes or improvements for the GNU C compiler, that is very helpful. Send suggested fixes to the patches -mailing list, @code{gcc-patches@@gcc.gnu.org}. +mailing list, @email{gcc-patches@@gcc.gnu.org}. Please follow these guidelines so we can study your patches efficiently. If you don't follow these guidelines, your information might still be @@ -2770,8 +2770,8 @@ ways to find it: @itemize @bullet @item Send a message to a suitable network mailing list. First try -@code{gcc-bugs@@gcc.gnu.org} or @code{bug-gcc@@gnu.org}, and if that -brings no response, try @code{gcc@@gcc.gnu.org}. +@email{gcc-bugs@@gcc.gnu.org} or @email{bug-gcc@@gnu.org}, and if that +brings no response, try @email{gcc@@gcc.gnu.org}. @item Look in the service directory for someone who might help you for a fee. @@ -2784,13 +2784,13 @@ GCC distribution. If you would like to help pretest GCC releases to assure they work well, or if you would like to work on improving GCC, please contact -the maintainers at @code{gcc@@gcc.gnu.org}. A pretester should +the maintainers at @email{gcc@@gcc.gnu.org}. A pretester should be willing to try to investigate bugs as well as report them. If you'd like to work on improvements, please ask for suggested projects or suggest your own ideas. If you have already written an improvement, please tell us about it. If you have not yet started work, it is useful -to contact @code{gcc@@gcc.gnu.org} before you start; the +to contact @email{gcc@@gcc.gnu.org} before you start; the maintainers may be able to suggest ways to make your extension fit in better with the rest of GCC and with other development plans. diff --git a/gcc/install.texi b/gcc/install.texi index 0be79c2c..ca201c7 100644 --- a/gcc/install.texi +++ b/gcc/install.texi @@ -1029,7 +1029,7 @@ compilers, you may need to add @samp{-Wf,-XNg1500 -Olimit 3000}. @item elxsi-elxsi-bsd The Elxsi's C compiler has known limitations that prevent it from -compiling GNU C. Please contact @code{mrs@@cygnus.com} for more details. +compiling GNU C. Please contact @email{mrs@@cygnus.com} for more details. @item dsp16xx A port to the AT&T DSP1610 family of processors. @@ -1250,7 +1250,7 @@ This configuration is intended for embedded systems. @item m68000-hp-bsd HP 9000 series 200 running BSD. Note that the C compiler that comes -with this system cannot compile GNU CC; contact @code{law@@cygnus.com} +with this system cannot compile GNU CC; contact @email{law@@cygnus.com} to get binaries of GNU CC for bootstrapping. @item m68k-altos @@ -1285,7 +1285,7 @@ GNU assembler with native coff generation by providing @samp{--with-gnu-as} to the configure script or use GNU assembler with dbx-in-coff encapsulation by providing @samp{--with-gnu-as --stabs}. For any problem with native assembler or for availability of the DPX/2 port of GAS, contact -@code{F.Pierresteguy@@frcl.bull.fr}. +@email{F.Pierresteguy@@frcl.bull.fr}. @item m68k-crds-unox Use @samp{configure unos} for building on Unos. diff --git a/gcc/invoke.texi b/gcc/invoke.texi index 4daafb4..ce71954 100644 --- a/gcc/invoke.texi +++ b/gcc/invoke.texi @@ -2829,7 +2829,7 @@ These two options are intended to be removed someday, once they have helped determine the efficacy of various approaches to improving loop optimizations. -Please let us (@code{gcc@@gcc.gnu.org} and @code{fortran@@gnu.org}) +Please let us (@email{gcc@@gcc.gnu.org} and @email{fortran@@gnu.org}) know how use of these options affects the performance of your production code. We're very interested in code that runs @emph{slower} |