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

Move two sentences a little bit later in 'when to submit' and slightly modify

Browse source 
the first one.  This is part of a larger set of changes that are coming.
This commit is contained in:
Mark Linimon 2005-10-20 06:28:37 +00:00
parent 08152952e4
commit 624ab6d711
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=26084
1 changed files with 6 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -127,14 +127,7 @@
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<para>Another thing is that if the system on which you experienced <para>A bug that can not be reproduced can rarely be
the bug is not fairly up-to-date, you should seriously consider
upgrading and trying to reproduce the problem on an up-to-date
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 has already fixed.</para>
<para>Finally, a bug that can not be reproduced can rarely be
fixed. If the bug only occurred once and you can not reproduce fixed. If the bug only occurred once and you can not reproduce
it, and it does not seem to happen to anybody else, chances are it, and it does not seem to happen to anybody else, chances are
none of the developers will be able to reproduce it or figure none of the developers will be able to reproduce it or figure
@ -144,6 +137,11 @@
these kinds of bugs are actually caused by failing hard drives these kinds of bugs are actually caused by failing hard drives
or overheating processors &mdash; you should always try to rule or overheating processors &mdash; you should always try to rule
out these causes, whenever possible, before submitting a PR.</para> out these causes, whenever possible, before submitting a PR.</para>
<para>Then you should ascertain whether or not the problem is
timely. There are few things
that will annoy a developer more than receiving a problem report
about a bug she has already fixed.</para>
</section> </section>
<section id="pr-prep"> <section id="pr-prep">