os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove all trailing whitespace.

Browse source
This commit is contained in:
Dag-Erling Smørgrav 2001-11-23 02:18:41 +00:00
parent 71749510f6
commit 027e0c2897
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=11276
1 changed files with 18 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
en_US.ISO8859-1/articles/problem-reports/article.sgml
View file

@ -13,9 +13,9 @@ FreeBSD Entities//EN"> %freebsd;
<article>
<articleinfo>
<title>Writing FreeBSD Problem Reports</title>
<pubdate>$FreeBSD$</pubdate>
<abstract>
<para>This article describes how to best formulate and submit a
problem report to the FreeBSD Project.</para>
@ -29,12 +29,12 @@ FreeBSD Entities//EN"> %freebsd;
</author>
</authorgroup>
</articleinfo>
<indexterm><primary>problem reports</primary></indexterm>
<sect1 id="pr-intro">
<title>Introduction</title>
<para>One of the most frustrating experiences one can have as a
software user is to submit a problem report only to have it
summarily closed with a terse and unhelpful explanation like
@ -59,7 +59,7 @@ FreeBSD Entities//EN"> %freebsd;
before submitting a PR, rather than treat it as a step-by-step
tutorial.</para>
</sect1>
<sect1 id="pr-when">
<title>When to submit a problem report</title>
@ -86,7 +86,7 @@ FreeBSD Entities//EN"> %freebsd;
<para>Some cases where it may be appropriate to submit a problem
report about something that is not a bug are:</para>
<itemizedlist>
<listitem>
<para>Requests for feature enhancments. It is generally a
@ -108,7 +108,7 @@ FreeBSD Entities//EN"> %freebsd;
system before submitting a problem report. There are few things
that will annoy a developer more than receiving a problem report
about a bug she's already fixed.</para>
<para>Finally, a bug that can't be reproduced can rarely be fixed.
If the bug only occurred once and you can't reproduce it, and it
doesn't seem to happen to anybody else, chances are none of the
@ -215,7 +215,7 @@ FreeBSD Entities//EN"> %freebsd;
<sect2>
<title>Filling out the template</title>
<para>The template consists of a list of fields, some of which
are pre-filled, and some of which have comments explaining
their purpose or listing acceptable values. Don't worry about
@ -340,12 +340,12 @@ FreeBSD Entities//EN"> %freebsd;
<para><literal>misc:</literal> anything that doesn't fit
in any of the other categories.</para>
</listitem>
<listitem>
<para><literal>ports:</literal> problems relating to the
ports tree.</para>
</listitem>
<listitem>
<para><literal>sparc:</literal> problems specific to the
Sparc platform.</para>
@ -356,28 +356,28 @@ FreeBSD Entities//EN"> %freebsd;
<listitem>
<para><emphasis>Class:</emphasis> Choose one of the
following:</para>
<itemizedlist>
<listitem>
<para><literal>sw-bug:</literal> software bugs.</para>
</listitem>
<listitem>
<para><literal>doc-bug:</literal> errors in
documentation.</para>
</listitem>
<listitem>
<para><literal>change-request:</literal> requests for
additional features or changes in existing
features.</para>
</listitem>
<listitem>
<para><literal>update:</literal> updates to ports or
other contributed software.</para>
</listitem>
<listitem>
<para><literal>maintainer-update:</literal> updates to
ports for which you are the maintainer.</para>
@ -457,9 +457,9 @@ FreeBSD Entities//EN"> %freebsd;
<para>This will read the specified file, validate the contents,
strip comments and send it off.</para>
</sect2>
</sect1>
<sect1 id="pr-followup">
<title>Follow-up</title>
@ -485,5 +485,5 @@ FreeBSD Entities//EN"> %freebsd;
above) saying that the PR can be closed, and, if possible,
explaining how or when the problem was fixed.</para>
</sect1>
</article>