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

problem-reports: formatting; pet igor

Browse source 
Translators can ignore.
This commit is contained in:
Eitan Adler 2018-08-12 09:18:26 +00:00
parent 00514be308
commit 1ce4d3682a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=52117
1 changed files with 13 additions and 12 deletions

25
en_US.ISO8859-1/articles/problem-reports/article.xml
View file

@ -198,7 +198,7 @@
versions</link>.</para>
<para>If the problem is in a port, consider filing a bug with the
upstream. The &os; Project can not fix all bugs in all
upstream. The &os; Project can not fix all bugs in all
software.</para>
</section>
@ -250,9 +250,9 @@
<listitem>
<para>Next, the searchable <link
xlink:href="https://bugs.freebsd.org/bugzilla/query.cgi">&os;
PR database</link> (Bugzilla). Unless the problem is recent
or obscure, there is a fair chance it has already been
reported.</para>
PR database</link> (Bugzilla). Unless the problem is
recent or obscure, there is a fair chance it has already
been reported.</para>
</listitem>
<listitem>
@ -529,7 +529,8 @@
<title>Before Beginning</title>
<para>Similar considerations apply to use of the
<link xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">web-based
<link
xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">web-based
PR submission form</link>. Be careful of cut-and-paste
operations that might change whitespace or other text
formatting.</para>
@ -805,9 +806,9 @@
Try to avoid speculating about the causes of the problem
unless you are certain that you are on the right track, as
it may mislead a developer into making incorrect
assumptions about the problem. It should include the
actions you need to take to reproduce the problem. If you
know any workaround, include it. It not only helps other
assumptions about the problem. It should include the
actions you need to take to reproduce the problem. If you
know any workaround, include it. It not only helps other
people with
the same problem work around it, but may also help a
developer understand the cause for the problem.</para>
@ -834,10 +835,10 @@
initial report, please submit a follow up. The number one
reason for a bug not getting fixed is lack of communication with
the originator. The easiest way is to use the comment
option on the individual PR's web page, which you can reach
from the <link
xlink:href="https://bugs.freebsd.org/bugzilla/query.cgi">PR
search page</link>.</para>
option on the individual PR's web page, which you can reach
from the <link
xlink:href="https://bugs.freebsd.org/bugzilla/query.cgi">PR
search page</link>.</para>
<para>If the problem report remains open after the problem has
gone away, just add a comment