This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[wwwdocs] Clean up references to Bugzilla, use https,...
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: gcc-patches at gcc dot gnu dot org
- Cc: Tobias Burnus <burnus at net-b dot de>
- Date: Sun, 29 Jun 2014 13:42:57 +0200 (CEST)
- Subject: [wwwdocs] Clean up references to Bugzilla, use https,...
- Authentication-results: sourceware.org; auth=none
Consistently use bug tracker versus bug database, Bugzilla (where
possible), or the like. Avoid some references altogether and refer
to our bugs/ pages instead of directly linking to Bugzilla in some.
Use https for all remaining links to our Bugzilla instance.
Committed.
Gerald
Index: news.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/news.html,v
retrieving revision 1.143
diff -u -r1.143 news.html
--- news.html 28 Jun 2014 08:14:41 -0000 1.143
+++ news.html 29 Jun 2014 11:16:00 -0000
@@ -745,7 +745,7 @@
<a href="https://gcc.gnu.org/ml/gcc/2000-10/msg00573.html";>new, hand-crafted
recursive-descent C++ parser</a> sponsored by the Los Alamos National
Laboratory. The new parser is more standard conforming and fixes many bugs
-(about 100 in our bug database alone) from the old YACC-derived parser.
+(about 100 in our bug tracker alone) from the old YACC-derived parser.
</dd>
<dt><b>December 4, 2002</b></dt>
Index: style.mhtml
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/style.mhtml,v
retrieving revision 1.124
diff -u -r1.124 style.mhtml
--- style.mhtml 11 Jun 2014 17:45:30 -0000 1.124
+++ style.mhtml 29 Jun 2014 11:16:00 -0000
@@ -224,7 +224,7 @@
<tr><td <nav-body-style> >
<a href="<get-var BACKPATH>bugs/#known">Known bugs</a><br />
<a href="<get-var BACKPATH>bugs/">How to report</a><br />
- <a href="https://gcc.gnu.org/bugzilla/";>Bug database</a><br />
+ <a href="https://gcc.gnu.org/bugzilla/";>Bug tracker</a><br />
· <a href="<get-var BACKPATH>bugs/management.html">Management</a>
</td></tr>
</table></td></tr>
Index: bugs/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/index.html,v
retrieving revision 1.114
diff -u -r1.114 index.html
--- bugs/index.html 28 Jun 2014 23:30:27 -0000 1.114
+++ bugs/index.html 29 Jun 2014 11:16:00 -0000
@@ -129,10 +129,10 @@
<h3><a name="where">Where to post it</a></h3>
<p>Please submit your bug report directly to the
-<a href="http://gcc.gnu.org/bugzilla/";>GCC bug database</a>.
+<a href="https://gcc.gnu.org/bugzilla/";>GCC bug tracker</a>.
</p>
-<p>The GCC bug database requires you to create an account with a valid
+<p>The GCC bug tracker requires you to create an account with a valid
e-mail address. This is not merely to be annoying. It's because in
the past spammers have filed fake bug reports, and fake attachments to
real bug reports, to distribute malware and to add links to their spam
Index: bugs/management.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/management.html,v
retrieving revision 1.30
diff -u -r1.30 management.html
--- bugs/management.html 3 Jan 2013 05:09:54 -0000 1.30
+++ bugs/management.html 29 Jun 2014 11:16:00 -0000
@@ -1,11 +1,11 @@
<html>
<head>
-<title>Maintaining the GCC Bugzilla database</title>
+<title>Managing Bugs (Bugzilla and the Testsuite)</title>
</head>
<body>
-<h1>Managing Bugs (Bugzilla and the testsuite)</h1>
+<h1>Managing Bugs (Bugzilla and the Testsuite)</h1>
<p>This section contains information mostly intended for GCC
contributors.</p>
@@ -14,16 +14,17 @@
<p>If you <em>find</em> a bug, but you are not fixing it (yet):</p>
<ol>
-<li>Create a (minimal) testcase and add a bug report including it to
-the bug database (Bugzilla).</li>
+<li>Create a (minimal) testcase and file a bug report including it to
+our bug tracker.</li>
<li>Enter the version number of the compiler in the <em>Known To
Fail</em> field. If you are reporting the bug against a release
branch, or the trunk, enter the version number of the next planned
release from that branch.</li>
</ol>
-<p>If you want to <em>provide additional information</em> about a bug in
-the database:</p>
+<p>If you want to <em>provide additional information</em> about an existing
+bug report:</p>
+
<ul>
<li>If the bug is a segmentation fault in the compiler,
<a href="segfault.html">provide information about its location</a>.
@@ -42,9 +43,9 @@
<ol>
<li>Check in your fixes.</li>
<li>If there is already a testcase in the testsuite, remove the XFAIL.
-Else, create a minimal testcase (maybe the bug database already provides one)
+Else, create a minimal testcase (maybe the bug tracker already provides one)
and add it to our testsuite, marking it as PASS.</li>
-<li>If there is an associated bug report in the database, close it.</li>
+<li>If there is an associated bug report in the tracker, close it.</li>
<li>If, after your fix, the bug is present on some release branches
but not others, update the <em>Known To Fail</em> and <em>Known To
Work</em> fields to indicate which versions still have the bug.</li>
@@ -57,7 +58,7 @@
The status and resolution fields define and track the life cycle of a
bug. In addition to their <a
-href="http://gcc.gnu.org/bugzilla/page.cgi?id=fields.html";>regular
+href="https://gcc.gnu.org/bugzilla/page.cgi?id=fields.html";>regular
descriptions</a>, we also use two adition status values:
<dl>
@@ -150,7 +151,7 @@
<h3>Keywords</h3>
<p>These are used to further classify the problem reports. Follow the link
-for a <a href="http://gcc.gnu.org/bugzilla/describekeywords.cgi";>complete
+for a <a href="https://gcc.gnu.org/bugzilla/describekeywords.cgi";>complete
list of the keywords including descriptions</a>.</p>
Index: bugs/reghunt.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/reghunt.html,v
retrieving revision 1.18
diff -u -r1.18 reghunt.html
--- bugs/reghunt.html 28 Jun 2014 08:14:41 -0000 1.18
+++ bugs/reghunt.html 29 Jun 2014 11:16:00 -0000
@@ -29,8 +29,8 @@
<p>If you've got sufficient disk space available, keep old install
tree around for use in finding small windows in which regressions
-occur. Some people who do this regularly add information to Bugzilla
-about particular problem reports for regressions.</p>
+occur. Some people who do this regularly add information to our
+bug tracker about particular problem reports for regressions.</p>
<p>Before you start your search, verify that you can reproduce the
problem with GCC built from the current sources. If not, the bug might
@@ -182,8 +182,8 @@
<h2 id="test">Run the test</h2>
-<p>Assuming that there is a self-contained test for the bug, as there
-usually is for bugs reported via Bugzilla, write a small script to run it
+<p>Assuming that there is a self-contained test for the bug, write a
+small script to run it
and to report whether it passed or failed. If you're automating your
search then the script should tell you whether the next compiler build
should use earlier or later GCC sources.</p>
Index: fortran/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/fortran/index.html,v
retrieving revision 1.33
diff -u -r1.33 index.html
--- fortran/index.html 28 Jun 2014 08:14:41 -0000 1.33
+++ fortran/index.html 29 Jun 2014 11:16:00 -0000
@@ -20,7 +20,7 @@
with the Fortran 95 Standard and includes legacy F77 support.
In addition, a significant number of Fortran 2003 and Fortran 2008
features are implemented. Please give it a try. If you encounter problems,
-contact us at the mailing list or file a problem report in bugzilla.</p>
+contact us at the mailing list or file a problem report.</p>
<p>GFortran development follows the open development process. We do
this to attract a diverse team of developers and to ensure that GFortran
@@ -64,7 +64,7 @@
Language standard [ISO/IEC 1539-1:1997(E)]. We are now well into
F2003 and F2008 features.
The <a href="https://gcc.gnu.org/wiki/GFortran";>GFortran
-wiki</a> and <a href="http://gcc.gnu.org/bugzilla/";>Bugzilla</a>
+wiki</a> and <a href="https://gcc.gnu.org/bugzilla/";>our bug tracker</a>
list features under development or yet to be implemented. Compiler
capability is quite extensive and includes nearly all g77 features.
We highly encourage users to move from g77, which is no longer
@@ -75,9 +75,7 @@
<p>We regularly update the
<a href="https://gcc.gnu.org/wiki/GFortran#news";>status</a>
-of the front end and run-time library development.
-For a TODO list, check <a href="http://gcc.gnu.org/bugzilla/";>Bugzilla</a>
-and the <a href="https://gcc.gnu.org/wiki/GFortran";>GFortran wiki</a>.</p>
+of the front end and run-time library development.</p>
<h2>Contributing</h2>
Index: projects/beginner.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/beginner.html,v
retrieving revision 1.60
diff -u -r1.60 beginner.html
--- projects/beginner.html 28 Jun 2014 07:45:17 -0000 1.60
+++ projects/beginner.html 29 Jun 2014 11:16:01 -0000
@@ -19,8 +19,7 @@
with C and the Unix programming environment. Do not despair if any
individual task seems daunting; there's probably an easier one. If
you have <em>no</em> programming skills, we can still use your <a
-href="documentation.html">help with documentation</a> or with the <a
-href="http://gcc.gnu.org/bugzilla/";>bug database</a>.</p>
+href="documentation.html">help with documentation</a> or our bug tracker.</p>
<p>We assume that you already know how to <a href="../svn.html">get the
latest sources</a>, configure and build the compiler, and run the test
Index: projects/documentation.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/documentation.html,v
retrieving revision 1.8
diff -u -r1.8 documentation.html
--- projects/documentation.html 28 Jun 2014 07:45:17 -0000 1.8
+++ projects/documentation.html 29 Jun 2014 11:16:01 -0000
@@ -233,9 +233,8 @@
<code>gcc/doc/trouble.texi</code>. Work out what they refer to, if
necessary by asking people who were involved in GCC development when
those bugs were documented. If a bug is no longer present, remove it
-from the list; if it is still present, file a bug report in the <a
-href="http://gcc.gnu.org/bugzilla/";>GCC bug tracking system</a> or
-fix the bug yourself.</p>
+from the list; if it is still present, <a href="../bugs/">file a bug
+report</a>.</p>
</body>
</html>
Index: projects/gupc.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/gupc.html,v
retrieving revision 1.7
diff -u -r1.7 gupc.html
--- projects/gupc.html 1 Nov 2012 23:02:06 -0000 1.7
+++ projects/gupc.html 29 Jun 2014 11:16:01 -0000
@@ -132,9 +132,8 @@
<h2>Reporting Bugs</h2>
-<p>Bugs in GUPC should be reported via
-<a href="http://gcc.gnu.org/bugzilla/";>GCC Bugzilla</a>. In all cases,
-please add "UPC" to the keywords field in the bug report.
+<p>Bugs in GUPC should be <a href="../bugs/">reported to the GCC bug tracker</a>.
+Please add "UPC" to the keywords field in the bug report.
</p>
<h2>Status</h2>
Index: projects/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/index.html,v
retrieving revision 1.69
diff -u -r1.69 index.html
--- projects/index.html 27 Jun 2014 18:53:32 -0000 1.69
+++ projects/index.html 29 Jun 2014 11:16:02 -0000
@@ -15,7 +15,7 @@
<li>If you are new to GCC, start with our list of <a
href="beginner.html">projects for beginner GCC hackers.</a></li>
<li>Investigate bugs and attempt to fix bugs in our <a
- href="http://gcc.gnu.org/bugzilla/";>bug tracking system</a>,
+ href="https://gcc.gnu.org/bugzilla/";>bug tracker</a>,
see whether they still are present in current GCC.</li>
<li><a href="../about.html#TODO">Projects for the GCC web pages.</a></li>
<li><a href="documentation.html">Projects for improving the GCC
Index: projects/gomp/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/gomp/index.html,v
retrieving revision 1.15
diff -u -r1.15 index.html
--- projects/gomp/index.html 28 Jun 2014 07:45:18 -0000 1.15
+++ projects/gomp/index.html 29 Jun 2014 11:16:02 -0000
@@ -52,9 +52,7 @@
<a href="../../svn.html">anonymous SVN</a>.</p>
<h2>Reporting Bugs</h2>
-<p>Bugs in GOMP should be reported via
-<a href="http://gcc.gnu.org/bugzilla/";>bugzilla</a>. In all cases,
-please add "openmp" to the keywords field in the bug report.</p>
+<p>Please add "openmp" to the keywords field when filing a bug report.</p>
<h2>Documentation</h2>
<p>libgomp, the GOMP support library, has
Index: projects/tree-ssa/vectorization.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/tree-ssa/vectorization.html,v
retrieving revision 1.30
diff -u -r1.30 vectorization.html
--- projects/tree-ssa/vectorization.html 28 Jun 2014 08:14:42 -0000 1.30
+++ projects/tree-ssa/vectorization.html 29 Jun 2014 11:16:03 -0000
@@ -544,7 +544,7 @@
<p> Also see <a href= "https://gcc.gnu.org/wiki/VectorizationTasks";>
https://gcc.gnu.org/wiki/VectorizationTasks</a>
- and a list of vectorizer missed-optimization PRs in GCC Bugzilla. </p>
+ and a list of vectorizer missed-optimization PRs in the GCC bug tracker.</p>
<h2><a name="oldnews">Previous News and Status</a></h2>