coar 98/03/26 03:54:53
Modified: . bug_report.html
Log:
Some HTML cleanup. (There should be *no* leading space inside
anchor text; it gives the highlighted link a tail. It's a SHOULD
in the HTML specs for browsers to ignore \w*$\w* between a container
start-tag and the first non-whitespace content character, but most
browsers ignore this. Hence no newlines or whitespace between
<LI> or <A HREF> and the text that follows.)
Revision Changes Path
1.11 +46 -35 apache-site/bug_report.html
Index: bug_report.html
===================================================================
RCS file: /export/home/cvs/apache-site/bug_report.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- bug_report.html 1998/03/25 23:47:31 1.10
+++ bug_report.html 1998/03/26 11:54:53 1.11
@@ -16,43 +16,52 @@
<P>Welcome to the Apache Bug Reporting Page! If you are having trouble
with Apache, please fill out a problem report form and submit it.
-Before you do that, though, <FONT COLOR="red">make <b>sure</b> you have
-done <b>all</b> of the following:</FONT></P>
+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>Verified that the bug exists in <A href="mirrors/">the most recent
version</A>
- of Apache. There are many bugs in the 1.1/tree that have been fixed
- in the 1.2 tree.
-<LI>Checked the <A href="docs/misc/known_bugs.html">known bugs</A> page.
-<LI>Checked the <A HREF="docs/misc/known_client_problems.html">known client
problems</A> page.
-<LI>Checked the <A href="docs/misc/compat_notes.html">compatibility
- notes</A> page.
-<LI>Followed the instructions in the <code>INSTALL</code> file correctly -
- you edited the <code>Configuration</code> file to set the right platform
- and ran the <code>Configure</code> script to create the new
- <code>Makefile</code>.
-<LI>Tried compiling with only the distributed set of modules and with
- no other patches (so that we can make sure it's an Apache bug and
- not a bug in a module or patch provided by someone else). It is
- frustrating to take time and effort to track down a problem only
- to figure out it caused by a broken third party module.
-<LI>Checked the <A HREF="docs/misc/FAQ.html">FAQ</A>.
-<LI>Searched the <A HREF="http://www.apache.org/bugdb.cgi";>bug report</A>
- database. When you are doing this, you should be sure to search
- closed problem reports in addition to open ones. Also note that
- the search is not keyword based, so it requires an exact match
- of what you enter to find anything.
+ <LI>Verified that the bug exists in <A HREF="mirrors/">the most recent
+ version</A> of Apache. There are many bugs in the 1.1/tree that have been
+ fixed in the 1.2 tree.
+ </LI>
+ <LI>Checked the <A HREF="docs/misc/known_bugs.html">known bugs</A> page.
+ </LI>
+ <LI>Checked the <A HREF="docs/misc/known_client_problems.html">known client
+ problems</A> page.
+ </LI>
+ <LI>Checked the <A HREF="docs/misc/compat_notes.html">compatibility
+ notes</A> page.
+ </LI>
+ <LI>Followed the instructions in the <CODE>INSTALL</CODE> file correctly -
+ you edited the <CODE>Configuration</CODE> file to set the right platform
+ and ran the <CODE>Configure</CODE> script to create the new
+ <CODE>Makefile</CODE>.
+ </LI>
+ <LI>Tried compiling with only the distributed set of modules and with
+ no other patches (so that we can make sure it's an Apache bug and
+ not a bug in a module or patch provided by someone else). It is
+ frustrating to take time and effort to track down a problem only
+ to figure out it caused by a broken third party module.
+ </LI>
+ <LI>Checked the <A HREF="docs/misc/FAQ.html">FAQ</A>.
+ </LI>
+ <LI>Searched the <A HREF="http://www.apache.org/bugdb.cgi";>bug report</A>
+ database. When you are doing this, you should be sure to search
+ closed problem reports in addition to open ones. Also note that
+ the search is not keyword based, so it requires an exact match
+ of what you enter to find anything.
+ </LI>
</OL>
<BLOCKQUOTE>
<STRONG>
If you're not sure that your problem is specifically related to a
- bug in Apache (ie. not something like a client problem or configuration
- problem), we strongly recommend that you check in the
- <A HREF="news:comp.infosystems.www.servers.unix";><SAMP>
- comp.infosystems.www.servers.unix</SAMP></A> or <A HREF=
- "news:comp.infosystems.www.servers.ms-windows";><SAMP>
- comp.infosystems.www.servers.ms-windows</SAMP></A> (depending on
+ bug in Apache (<EM>i.e.</EM>, not something like a client problem or
+ configuration problem), we strongly recommend that you check in the
+ <A HREF="news:comp.infosystems.www.servers.unix";
+ ><SAMP>comp.infosystems.www.servers.unix</SAMP></A> or
+ <A HREF="news:comp.infosystems.www.servers.ms-windows";
+ ><SAMP>comp.infosystems.www.servers.ms-windows</SAMP></A> (depending on
the platform being used) Usenet newsgroup first. 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
@@ -60,14 +69,16 @@
developer time free for improving Apache. Most bug reports submitted
are actually user configuration problems that could be easily
fixed by asking in the newsgroup.
-
- <P>If you do not have access to a Usenet server, there are
+ <P>
+ If you do not have access to a Usenet server, there are
several web sites on the Internet that allow you to read and post
to Usenet, such as <A HREF="http://www.dejanews.com/";>Deja News</A>.
-
- <P><FONT COLOR="red">Do <B>not</B> post to Usenet and submit a bug
+ </P>
+ <P>
+ <FONT COLOR="red">Do <STRONG>not</STRONG> post to Usenet and submit a bug
report at the same time.</FONT> This wastes everyone's time.
Post to Usenet and wait a few days.
+ </P>
</STRONG>
</BLOCKQUOTE>
@@ -80,7 +91,7 @@
<P>
If your browser is incapable of using forms, please submit the same
information to
-<A href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>.
+<A HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>.
</P>
<H1>Do NOT send configuration questions or requests for help debugging
CGI!</H1>
</BODY>
