httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r816203 - in /websites/staging/httpd/trunk/content: ./ bug_report.html
Date Sun, 06 May 2012 23:45:55 GMT
Author: buildbot
Date: Sun May  6 23:45:55 2012
New Revision: 816203

Log:
Staging update by buildbot for httpd

Modified:
    websites/staging/httpd/trunk/content/   (props changed)
    websites/staging/httpd/trunk/content/bug_report.html

Propchange: websites/staging/httpd/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun May  6 23:45:55 2012
@@ -1 +1 @@
-1334833
+1334835

Modified: websites/staging/httpd/trunk/content/bug_report.html
==============================================================================
--- websites/staging/httpd/trunk/content/bug_report.html (original)
+++ websites/staging/httpd/trunk/content/bug_report.html Sun May  6 23:45:55 2012
@@ -73,8 +73,10 @@
         <div id="apcontents">
             
             <h1 id="bug-reporting">Bug Reporting</h1>
-<p><strong>Reports of security issues should <em>not</em> be made
here. Please see the <a href="security_report.html">security report page</a> if
you have concerns or think you have discovered a security hole in the Apache Web server software.</strong>

-If you have identified a bug in the Apache HTTP Server, please fill out a problem report
form and submit it. Before you do that, though,&lt;font color="red"&gt;make <strong>sure</strong>
you have done <strong>all</strong> of the following:&lt;/font&gt;</p>
+<p><strong>Reports of security issues should <em>not</em> be made
here. Please see the <a href="security_report.html">security report page</a>
+if you have concerns or think you have discovered a security hole in the Apache Web server
software.</strong> 
+If you have identified a bug in the Apache HTTP Server, please fill out a problem report
form and submit it.
+Before you do that, though, <font color="red">make <strong>sure</strong>
you have done <strong>all</strong> of the following:</font></p>
 <ol>
 <li>
 <p>Verified that the bug exists in <a href="/download.cgi">the most recent version</a>
of Apache.</p>
@@ -104,9 +106,15 @@ If you have identified a bug in the Apac
 <p><a href="http://issues.apache.org/bugzilla/buglist.cgi?changedin=10&amp;amp;product=Apache+httpd-2">All
bugs changed in the last 10 days</a> </p>
 </li>
 </ol>
-<p>Unless you are sure that you have found a bug in the Apache HTTP Server, we strongly
recommend that you try the <a href="userslist.html">Apache HTTP Server Users List</a>
before using the bug database. If you don't receive a response within a few days, then please
submit it to the Apache bug database. If it's a known issue, you'll probably get a faster
response from the mailing list and you will help keep developer time free for improving Apache.
Most bug reports submitted are actually user configuration problems that could be easily fixed
by asking on the mailing list.</p>
-<p>Do <strong>not</strong> post to the mailing list and submit a bug report
at the same time. This wastes everyone's time. Post to the mailing list and wait a few days
before submitting a bug report.</p>
-<p>If you have done all of the preceding, then please select the button below and fill
out the form. We will respond to it as soon as we can.</p>
+<p>Unless you are sure that you have found a bug in the Apache HTTP Server, we strongly
recommend that you try the
+<a href="userslist.html">Apache HTTP Server Users List</a> before using the bug
database. If you don't receive a response
+within a few days, then please submit it to the Apache bug database. If it's a known issue,
you'll probably get
+a faster response from the mailing list and you will help keep developer time free for improving
Apache. Most
+bug reports submitted are actually user configuration problems that could be easily fixed
by asking on the mailing list.</p>
+<p>Do <strong>not</strong> post to the mailing list and submit a bug report
at the same time. This wastes everyone's time.
+Post to the mailing list and wait a few days before submitting a bug report.</p>
+<p>If you have done all of the preceding, then please select the button below and fill
out the form.
+We will respond to it as soon as we can.</p>
 <ul>
 <li>
 <p><strong>Do NOT send configuration questions or requests for help debugging
CGI!</strong> </p>
@@ -115,7 +123,8 @@ If you have identified a bug in the Apac
 <p><strong>If you're tracing spam or you're here because one of your favourite
Web sites now says 'It Worked! Apache is installed!' -- then contact the mail originator or
the Web site's Webmaster directly, because they're just using our software and we have nothing
to do with them. Don't waste your time, or ours, by telling us about it.</strong> </p>
 </li>
 </ul>
-<p>Use the <a href="http://issues.apache.org/bugzilla/">Apache Bug Database</a>
to submit bug reports. The appropriate Bugzilla project for Apache HTTPD is "Apache httpd-2"
and "Apache httpd-2.0".</p>
+<p>Use the <a href="http://issues.apache.org/bugzilla/">Apache Bug Database</a>
to submit bug reports. The appropriate
+Bugzilla project for Apache HTTPD is "Apache httpd-2" and "Apache httpd-2.0".</p>
             
 
             <!-- FOOTER -->



Mime
View raw message