Gerald Pfeifer suggested using active voice on the discussion of the Algol 68 patch[1]. So I used active voice on all the other lists to keep the style the same. I also changed the rust list description to match the others.
CC'ing all the docs co-maintainers too. Ok for the site? [1] https://inbox.sourceware.org/gcc-patches/[email protected]/T/# -- >8 -- Make lists descriptions more consistent. Signed-off-by: Pietro Monteiro <[email protected]> --- htdocs/lists.html | 34 ++++++++++++++++------------------ 1 file changed, 16 insertions(+), 18 deletions(-) diff --git a/htdocs/lists.html b/htdocs/lists.html index 5ffd20e1..20103c68 100644 --- a/htdocs/lists.html +++ b/htdocs/lists.html @@ -58,9 +58,8 @@ before <a href="#subscribe">subscribing</a> and posting to these lists. <li><b><a href="https://gcc.gnu.org/ml/gcc-patches/";>gcc-patches</a></b> 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> + particular patches. Send all patches (including those for front ends and web + pages) and all discussion for a particular patch 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 @@ -71,33 +70,32 @@ before <a href="#subscribe">subscribing</a> and posting to these lists. are posted.</li> <li><b><a href="https://gcc.gnu.org/ml/gcc-rust/";>gcc-rust</a></b> - is for discussing <a href="https://gcc.gnu.org/wiki/RustFrontEnd";>Rust - support in GCC</a>. - Patches should be sent to both this list and <b>gcc-patches</b>.</li> + is the main discussion and development list for the + <a href="https://gcc.gnu.org/wiki/RustFrontEnd";>Rust language front end</a> of + GCC, and the corresponding runtime library. Send gccrs and libgrust patches + to both <b>gcc-rust</b> and <b>gcc-patches</b>.</li> <li><b><a href="https://gcc.gnu.org/ml/libstdc++/";>libstdc++</a></b> 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> + library (libstdc++-v3). Send libstdc++-v3 patches to both <b>libstdc++</b> + and <b>gcc-patches</b>.</li> <li><b><a href="https://gcc.gnu.org/ml/fortran/";>fortran</a></b> 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> + front end of GCC, and the corresponding runtime library. Send gfortran and + libgfortran patches to both <b>fortran</b> and <b>gcc-patches</b>.</li> <li><b><a href="https://gcc.gnu.org/ml/jit/";>jit</a></b> - is for discussion and development of + is the main discussion and development list for <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. The list is intended for both users and developers of the library. - Patches for the jit branch should go to both this list and - <b>gcc-patches</b>.</li> + Send libgccjit patches to both <b>jit</b> and <b>gcc-patches</b>.</li> <li><b><a href="https://gcc.gnu.org/ml/algol68/";>algol68</a></b> is the discussion and development list for the Algol 68 language front - end of GCC, and the corresponding runtime library. Patches to ga68 - and libga68 should be sent to both this list and <b>gcc-patches</b>.</li> + end of GCC, and the corresponding runtime library. Send ga68 and libga68 + patches to both <b>algol68</b> and <b>gcc-patches</b>.</li> <li><b><a href="https://gcc.gnu.org/ml/gnutools-advocacy/";>gnutools-advocacy</a></b> is for discussion of marketing, promotion, recruiting and advocacy for @@ -149,8 +147,8 @@ before <a href="#subscribe">subscribing</a> and posting to these lists. <li><b><a href="https://gcc.gnu.org/ml/java-patches/";>java-patches</a></b> was a list for submission and discussion of patches to libgcj, the - Java runtime. Patches to GCJ, the Java language front end, should have - gone to both this list and <b>gcc-patches</b>.</li> + Java runtime. Patches to GCJ, the Java language front end, were sent + to both this list and <b>gcc-patches</b>.</li> <li><b><a href="https://gcc.gnu.org/ml/java-prs/";>java-prs</a></b> was a read-only list which tracked Java-related problem reports as -- 2.43.0
