On 24/04/20 12:17 +0100, Jonathan Wakely wrote:
On 24/04/20 12:57 +0200, Gerald Pfeifer wrote:
On Thu, 23 Apr 2020, Jonathan Wakely wrote:
This no longer works, so direct people to the mailman listinfo pages
instead.
OK to commit to wwwdocs?
Yes, thank you!
I was wondering whether we could keep something similar to this nice
form, but could not come up with a good way. So a regression we'll
swallow as part of the system migration.
We could link directly to the listinfo page for each list, to get
there in a single click. We can add that later, for now I wanted a
quick fix for the broken form (and I've pushed that change).
We could just add a link after the name of each list, as in this
patch.
What do you think?
We could replace the text "(info)" with an icon like
https://en.wikipedia.org/wiki/File:Information_icon.svg
if we want to be "fancy" ;-)
diff --git a/htdocs/gcc-10/porting_to.html b/htdocs/gcc-10/porting_to.html
index 9574aacc..1f118ca6 100644
--- a/htdocs/gcc-10/porting_to.html
+++ b/htdocs/gcc-10/porting_to.html
@@ -73,6 +73,18 @@ were implicitly defined after including unrelated headers such as
Correct code should include the appropriate headers for the classes being used.
</p>
+<h3 id="namespace-pollution">Names not redeclared in <code>__gnu_cxx</code></h3>
+
+<p>
+In previous releases a number of names from namespace <code>std</code> were
+redeclared in namespace <code>__gnu_cxx</code>. This meant that names such as
+<code>__gnu_cxx::pair</code>, <code>__gnu_cxx::vector</code>, and
+<code>__gnu_cxx::size_t</code> were aliases for <code>std::pair</code>,
+<code>std::vector</code>, and <code>std::size_t</code>. These aliases were only
+present as implementation details and were never meant to be part of the
+public API. The aliases have been removed, so names from namespace
+<code>std</code> should be qualified with <code>std::</code>.
+</p>
<h2 id="fortran">Fortran language issues</h2>
diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index 97d60870..3f638249 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -271,7 +271,14 @@ made after you called <code>git add</code> for them.</strong></li>
<li>After exiting the editor, Git will check in your
changes <strong>locally</strong>. When your prompt returns
the <strong>local</strong> checkin is finished, but you still need to
-push the changes to the shared repository; do <code>git push</code>.
+push the changes to the shared repository. Before pushing it to gcc.gnu.org,
+make sure your local branch only contains the changes you expect,
+e.g. by reviewing the <code>git status</code> or <code>git log</code> output.
+Once you're ready to publish the changes, do <code>git push</code>,
+or to be more explicit,
+<code>git push origin HEAD:<i><target branch></i></code>,
+where <code><i><target branch></i></code> is the branch on the remote,
+such as <code>master</code> or <code>releases/gcc-9</code>.
A message will be sent to the gcc-cvs mailing list indicating that a
change was made. If <code>git push</code> gives an error because
someone else has pushed their own changes to the same branch,
diff --git a/htdocs/lists.html b/htdocs/lists.html
index ea37aedc..b6bbfaf5 100644
--- a/htdocs/lists.html
+++ b/htdocs/lists.html
@@ -26,6 +26,7 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
<ul>
<li><b><a href="https://gcc.gnu.org/ml/gcc-announce/";>gcc-announce</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/gcc-announce";>(info)</a>
is a read-only low volume list where
we post announcements about releases or other important events.</li>
</ul>
@@ -34,10 +35,12 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
<ul>
<li><b><a href="https://gcc.gnu.org/ml/gcc-help/";>gcc-help</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/gcc-help";>(info)</a>
is a relatively high volume list for people searching for help in
building or using GCC.</li>
<li><p><b><a href="https://gcc.gnu.org/ml/gcc/";>gcc</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/gcc";>(info)</a>
is a high volume list for general development discussions about GCC.
Anything relevant to the development or testing of GCC and not
covered by other mailing lists is suitable for discussion here.</p>
@@ -53,35 +56,43 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
development process.</p></li>
<li><b><a href="https://gcc.gnu.org/ml/gcc-bugs/";>gcc-bugs</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/gcc-bugs";>(info)</a>
is a relatively high volume list with mails from our
bug-tracking system.</li>
<li><b><a href="https://gcc.gnu.org/ml/gcc-patches/";>gcc-patches</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/gcc-patches";>(info)</a>
is a relatively high volume list for patch submissions and discussion of
particular patches. All patches (including those for front ends and web
pages) and all discussion for a particular patch should be sent to this
list.</li>
<li><b><a href="https://gcc.gnu.org/ml/gcc-testresults/";>
- gcc-testresults</a></b> is a moderate volume list where test results for
+ gcc-testresults</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/gcc-testresults";>(info)</a>
+ is a moderate volume list where test results for
the GCC compilers are posted.</li>
<li><b><a href="https://gcc.gnu.org/ml/gcc-regression/";>gcc-regression</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/gcc-regression";>(info)</a>
is a moderate volume list where regression results for the GCC compilers
are posted.</li>
<li><b><a href="https://gcc.gnu.org/ml/libstdc++/";>libstdc++</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/libstdc++";>(info)</a>
is the main discussion and development list for the standard C++
library (libstdc++-v3). Patches to libstdc++-v3 should be sent to
both this list and <b>gcc-patches</b>.</li>
<li><b><a href="https://gcc.gnu.org/ml/fortran/";>fortran</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/fortran";>(info)</a>
is the main discussion and development list for the Fortran language
front end of GCC, and the corresponding runtime library. Patches to
gfortran and libgfortran should go to both this list and
<b>gcc-patches</b>.</li>
<li><b><a href="https://gcc.gnu.org/ml/jit/";>jit</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/jit";>(info)</a>
is for discussion and development of
<a href="https://gcc.gnu.org/wiki/JIT";>libgccjit</a>, an experimental
library for implementing Just-In-Time compilation using GCC as a back end.
@@ -90,6 +101,7 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
<b>gcc-patches</b>.</li>
<li><b><a href="https://gcc.gnu.org/ml/gnutools-advocacy/";>gnutools-advocacy</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/gnutools-advocacy";>(info)</a>
is for discussion of marketing, promotion, recruiting and advocacy for
the entire GNU Toolchain (Binutils, GAS, GCC, GDB, GLIBC, GLD, and Gold).</li>
</ul>
@@ -98,19 +110,23 @@ before <a href="#subscribe">subscribing</a> and posting to these lists.
<ul>
<li><b><a href="https://gcc.gnu.org/ml/gcc-cvs/";>gcc-cvs</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/gcc-cvs";>(info)</a>
is a read-only, relatively high volume list which tracks checkins to the
GCC source repository.</li>
<li><b><a href="https://gcc.gnu.org/ml/libstdc++-cvs/";>libstdc++-cvs</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/libstdc++-cvs";>(info)</a>
is a read-only, relatively low volume list which tracks checkins to
the libstdc++-v3 part of the GCC repository. This is a subset
of the messages to <b>gcc-cvs</b>.</li>
<li><b><a href="https://gcc.gnu.org/ml/gcc-cvs-wwwdocs/";>gcc-cvs-wwwdocs</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/gcc-cvs-wwwdocs";>(info)</a>
is a read-only, relatively low volume list which tracks checkins to
the GCC webpages repository.</li>
<li><b><a href="https://gcc.gnu.org/ml/gccadmin/";>gccadmin</a></b>
+ <a href="https://gcc.gnu.org/mailman/listinfo/gccadmin";>(info)</a>
is a read-only moderate volume list where output from
<code>cron</code> jobs run by the <code>gccadmin</code> account on
gcc.gnu.org is posted.</li>
@@ -195,8 +211,7 @@ it's assumed that no-one on these lists means to speak for their company.</p>
<h2 id="subscribe">Subscribing/unsubscribing</h2>
<p>You can subscribe or unsubscribe from any of the GCC mailing
-lists by clicking on the list name above and then following the
-"more information about this list" link.</p>
+lists by following the "(info") links above.</p>
<p>If you're having trouble getting off a list, look at the
<b><code>List-Unsubscribe:</code></b> header on a message sent to that list.
