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

Minor readability changes.

Browse source
This commit is contained in:
Maxim Sobolev 2002-02-04 06:50:41 +00:00
parent d18bdbf627
commit a9331b62d7
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=12075
1 changed files with 6 additions and 6 deletions

12
en/gnome/docs/bugging.sgml
View file

@ -17,11 +17,11 @@
<p>The rule of the thumb should be: report as much information as you
can, because even if there is some irrelevant information usually
developers could quite easy filter it out. On contrary, situation is
much worse when there is too little information to reliably track down
or reproduce the problem - in this case developers have to spend their
time guessing and/or asking originator of report to send more
information.</p>
developers could quite easy filter it out. On the contrary, the
situation is much worse when there is too little information to
reliably track down or reproduce the problem - in this case developers
have to spend their time guessing and/or asking originator of report
to send more information.</p>
<p>There are plenty of examples of totally useless bug reports, something
like <i>"Hey, gnomefoo port is broken. I'm running FreeBSD-X.Y.
@ -56,7 +56,7 @@
<p>There are several ways to report a bug in GNOME running on a FreeBSD
system: you could send report to the
<a href="mailto:freebsd-gnome@FreeBSD.org">freebsd-gnome mailing
<a href="mailto:&email;@FreeBSD.org">freebsd-gnome mailing
list</a>, file a problem report in
<a href="http://www.freebsd.org/support.html#gnats">FreeBSD bug
reporting system</a>, send your report to the particular GNOME