From: Gerald Pfeifer <gerald@pfeifer.com>
To: Phil Edwards <phil@jaj.com>
Cc: "Manuel López-Ibáñez" <lopezibanez@gmail.com>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [wwwdocs] PATCH for Re: Creating gcc-newbies mailing list
Date: Fri, 27 Jul 2007 22:38:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0707280032040.19878@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20070727211904.GA9669@disaster.jaj.com>
On Fri, 27 Jul 2007, Phil Edwards wrote:
> Putting gcc-help as the first address mentioned in lists.html is a
> good idea.
That's a good idea. Done thusly.
Gerald
Index: lists.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/lists.html,v
retrieving revision 1.100
diff -u -3 -p -r1.100 lists.html
--- lists.html 19 Nov 2006 15:28:11 -0000 1.100
+++ lists.html 27 Jul 2007 22:31:26 -0000
@@ -37,6 +37,10 @@ before <a href="#subscribe">subscribing<
<p>Open lists:</p>
<ul>
+ <li><b><a href="http://gcc.gnu.org/ml/gcc-help/">gcc-help</a></b>
+ is a relatively high volume list for people searching for help in
+ building or using GCC.</li>
+
<li><p><b><a href="http://gcc.gnu.org/ml/gcc/">gcc</a></b>
is a high volume list for general development discussions about GCC.
Anything relevant to the development or testing of GCC and not
@@ -53,10 +57,6 @@ before <a href="#subscribe">subscribing<
sufficient to follow the major trends and important news in GCC's
development process.</p></li>
- <li><b><a href="http://gcc.gnu.org/ml/gcc-help/">gcc-help</a></b>
- is a relatively high volume list for people searching for help in building
- or using GCC.</li>
-
<li><b><a href="http://gcc.gnu.org/ml/gcc-bugs/">gcc-bugs</a></b>
is a relatively high volume list with mails from our Bugzilla
bug-tracking system.</li>
parent reply other threads:[~2007-07-27 22:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20070727211904.GA9669@disaster.jaj.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0707280032040.19878@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=lopezibanez@gmail.com \
--cc=phil@jaj.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).