summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJustin Erenkrantz <jerenkrantz@apache.org>2001-08-22 18:27:53 +0000
committerJustin Erenkrantz <jerenkrantz@apache.org>2001-08-22 18:27:53 +0000
commit5904f3f22d19ea54081bca7abb48f97ada9cde65 (patch)
treea6ead328149e3f532e20fae1578e70d97896a017
parentd001e336640b8ea3c4aeb0c7452014869c9eff36 (diff)
downloadhttpd-5904f3f22d19ea54081bca7abb48f97ada9cde65.tar.gz
Change the new-httpd@apache.org references to dev@httpd.apache.org.
There are some references just to "new-httpd" throughout - I left these intact as I'm not sure what the nickname for the new list is (dev@httpd?). git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@90498 13f79535-47bb-0310-9956-ffa450edef68
-rw-r--r--ABOUT_APACHE10
-rw-r--r--docs/manual/misc/FAQ-B.html6
2 files changed, 8 insertions, 8 deletions
diff --git a/ABOUT_APACHE b/ABOUT_APACHE
index 6d47a5a882..2c9c17d241 100644
--- a/ABOUT_APACHE
+++ b/ABOUT_APACHE
@@ -149,13 +149,13 @@ of it in serious need of updating) to be found at <http://dev.apache.org/>.
If you'd like to become an active contributor to the Apache project (the
group of volunteers who vote on changes to the distributed server), then
-you need to start by subscribing to the new-httpd@apache.org mailing list.
+you need to start by subscribing to the dev@httpd.apache.org mailing list.
One warning though: traffic is high, 1000 to 1500 messages/month.
-To subscribe to the list, send "subscribe new-httpd" in the body of
-a message to <majordomo@apache.org>. We recommend reading the list for
-a while before trying to jump in to development.
+To subscribe to the list, send "subscribe dev" in the body of
+a message to <dev-subscribe@httpd.apache.org>. We recommend reading the
+list for a while before trying to jump in to development.
- NOTE: The developer mailing list (new-httpd@apache.org) is not
+ NOTE: The developer mailing list (dev@httpd.apache.org) is not
a user support forum; it is for people actively working on development
of the server code and documentation, and for planning future
directions. If you have user/configuration questions, send them
diff --git a/docs/manual/misc/FAQ-B.html b/docs/manual/misc/FAQ-B.html
index 054914c415..6a401f5661 100644
--- a/docs/manual/misc/FAQ-B.html
+++ b/docs/manual/misc/FAQ-B.html
@@ -31,7 +31,7 @@
<!--#include virtual="header.html" -->
<H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
<P>
- $Revision: 1.7 $ ($Date: 2001/03/28 21:26:29 $)
+ $Revision: 1.8 $ ($Date: 2001/08/22 18:23:09 $)
</P>
<P>
The latest version of this FAQ is always available from the main
@@ -292,12 +292,12 @@
</P>
<P>
In general, the first course of action is to be a member of the
- <SAMP>new-httpd@apache.org</SAMP> mailing list. This indicates to
+ <SAMP>dev@httpd.apache.org</SAMP> mailing list. This indicates to
the Group that you are closely following the latest Apache
developments. Your patch file should be generated using either
'<CODE>diff&nbsp;-c</CODE>' or '<CODE>diff&nbsp;-u</CODE>' against
the latest CVS tree. To submit your patch, send email to
- <SAMP>new-httpd@apache.org</SAMP> with a <SAMP>Subject:</SAMP> line
+ <SAMP>dev@httpd.apache.org</SAMP> with a <SAMP>Subject:</SAMP> line
that starts with <SAMP>[PATCH]</SAMP> and includes a general
description of the patch. In the body of the message, the patch
should be clearly described and then included at the end of the