diff options
| author | Justin Erenkrantz <jerenkrantz@apache.org> | 2001-08-22 18:27:53 +0000 |
|---|---|---|
| committer | Justin Erenkrantz <jerenkrantz@apache.org> | 2001-08-22 18:27:53 +0000 |
| commit | 5904f3f22d19ea54081bca7abb48f97ada9cde65 (patch) | |
| tree | a6ead328149e3f532e20fae1578e70d97896a017 /docs | |
| parent | d001e336640b8ea3c4aeb0c7452014869c9eff36 (diff) | |
| download | httpd-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
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/manual/misc/FAQ-B.html | 6 |
1 files changed, 3 insertions, 3 deletions
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 -c</CODE>' or '<CODE>diff -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 |