You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by tr...@apache.org on 2003/06/24 00:59:44 UTC
cvs commit: httpd-site/docs/dev patches.html
trawick 2003/06/23 15:59:44
Modified: xdocs/dev patches.xml
docs/dev patches.html
Log:
point to the new bug db
PR: 20958
Revision Changes Path
1.5 +2 -2 httpd-site/xdocs/dev/patches.xml
Index: patches.xml
===================================================================
RCS file: /home/cvs/httpd-site/xdocs/dev/patches.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- patches.xml 19 Jun 2002 03:55:11 -0000 1.4
+++ patches.xml 23 Jun 2003 22:59:44 -0000 1.5
@@ -68,8 +68,8 @@
your patch in a week or so if you have not yet received any feedback
from the developers' group. Another good way to make sure it gets
on our plate is to submit it through the bug database, at <a
-href="http://bugs.apache.org/">http://bugs.apache.org/</a>, marking
-it as a "change-request".</p>
+href="http://nagoya.apache.org/bugzilla/">
+http://nagoya.apache.org/bugzilla/</a>.</p>
<p>Be aware that the core developers tend to be very conservative
about what makes it into the core of Apache. Apache has a very
1.20 +4 -2 httpd-site/docs/dev/patches.html
Index: patches.html
===================================================================
RCS file: /home/cvs/httpd-site/docs/dev/patches.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- patches.html 28 Dec 2002 21:12:18 -0000 1.19
+++ patches.html 23 Jun 2003 22:59:44 -0000 1.20
@@ -131,8 +131,10 @@
vacation, it could get lost in the noise. Feel free to resubmit
your patch in a week or so if you have not yet received any feedback
from the developers' group. Another good way to make sure it gets
-on our plate is to submit it through the bug database, at <a href="http://bugs.apache.org/">http://bugs.apache.org/</a>, marking
-it as a "change-request".</p>
+on our plate is to submit it through the bug database, at <a
+href="http://nagoya.apache.org/bugzilla/">
+http://nagoya.apache.org/bugzilla/</a>.</p>
+
<p>Be aware that the core developers tend to be very conservative
about what makes it into the core of Apache. Apache has a very
flexible API, and any advanced functionality is likely to be pushed