Return-Path: X-Original-To: apmail-httpd-cvs-archive@www.apache.org Delivered-To: apmail-httpd-cvs-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 93805C073 for ; Sun, 6 May 2012 23:46:13 +0000 (UTC) Received: (qmail 79199 invoked by uid 500); 6 May 2012 23:46:13 -0000 Delivered-To: apmail-httpd-cvs-archive@httpd.apache.org Received: (qmail 79135 invoked by uid 500); 6 May 2012 23:46:13 -0000 Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list cvs@httpd.apache.org Received: (qmail 79116 invoked by uid 99); 6 May 2012 23:46:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 May 2012 23:46:13 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 May 2012 23:46:10 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 5C1FF23888CD; Sun, 6 May 2012 23:45:49 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1334835 - /httpd/site/trunk/content/bug_report.mdtext Date: Sun, 06 May 2012 23:45:49 -0000 To: cvs@httpd.apache.org From: joes@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120506234549.5C1FF23888CD@eris.apache.org> Author: joes Date: Sun May 6 23:45:48 2012 New Revision: 1334835 URL: http://svn.apache.org/viewvc?rev=1334835&view=rev Log: various formatting issues Modified: httpd/site/trunk/content/bug_report.mdtext Modified: httpd/site/trunk/content/bug_report.mdtext URL: http://svn.apache.org/viewvc/httpd/site/trunk/content/bug_report.mdtext?rev=1334835&r1=1334834&r2=1334835&view=diff ============================================================================== --- httpd/site/trunk/content/bug_report.mdtext (original) +++ httpd/site/trunk/content/bug_report.mdtext Sun May 6 23:45:48 2012 @@ -1,9 +1,11 @@ Title: Bug Reporting - # Bug Reporting # - **Reports of security issues should *not* be made here. Please see the [security report page](security_report.html) if you have concerns or think you have discovered a security hole in the Apache Web server software.** -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 **sure** you have done **all** of the following:</font> + + **Reports of security issues should *not* be made here. Please see the [security report page](security_report.html) +if you have concerns or think you have discovered a security hole in the Apache Web server software.** +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, make **sure** you have done **all** of the following: 1. Verified that the bug exists in [the most recent version](/download.cgi) of Apache. @@ -25,15 +27,22 @@ If you have identified a bug in the Apac - [All bugs changed in the last 10 days](http://issues.apache.org/bugzilla/buglist.cgi?changedin=10&product=Apache+httpd-2) -Unless you are sure that you have found a bug in the Apache HTTP Server, we strongly recommend that you try the [Apache HTTP Server Users List](userslist.html) 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. +Unless you are sure that you have found a bug in the Apache HTTP Server, we strongly recommend that you try the +[Apache HTTP Server Users List](userslist.html) 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. -Do **not** 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. +Do **not** 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. -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. +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. - **Do NOT send configuration questions or requests for help debugging CGI!** - **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.** -Use the [Apache Bug Database](http://issues.apache.org/bugzilla/) to submit bug reports. The appropriate Bugzilla project for Apache HTTPD is "Apache httpd-2" and "Apache httpd-2.0". +Use the [Apache Bug Database](http://issues.apache.org/bugzilla/) to submit bug reports. The appropriate +Bugzilla project for Apache HTTPD is "Apache httpd-2" and "Apache httpd-2.0".