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

Improvement on the grammar and reword.

Browse source 
Submitted by:	ceri (Thanks!)
This commit is contained in:
Jeremy Messenger 2006-01-07 05:53:18 +00:00
parent 3ca87e0536
commit 2e83cc24dc
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=26795
1 changed files with 11 additions and 9 deletions

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

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/bugging.sgml,v 1.21 2005/12/29 06:42:27 adamw Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/bugging.sgml,v 1.22 2006/01/06 22:20:05 mezz Exp $">
<!ENTITY title "FreeBSD GNOME Project: Reporting a Bug">
<!ENTITY % navincludes SYSTEM "../includes.navgnome.sgml"> %navincludes;
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
@ -27,9 +27,9 @@
or is a bug in an application that would affect all users,
on all operating systems. If you cannot determine if the
problem is FreeBSD-specific or not, then send your
problem to <a
problem to the <a
href="mailto:&email;@FreeBSD.org">freebsd-gnome mailing
list</a>, and we can help decided where the problem lies.
list</a>, and we can help decide where the problem lies.
</ul>
<h2>2. What to report?</h2>
@ -56,16 +56,18 @@
<li><p>Information specific for each type of breakage:</p>
<ul>
<li>If a port will not build, provide a full log of the
unsuccessful build by either upload in any website,
unsuccessful build by either uploading it to any website,
copy-n-paste in <a
href="http://freebsd-gnome.pastebin.com">http://freebsd-gnome.pastebin.com</a>,
or send-pr with attach. Try to avoid send any attach to
the mailing list, because the list usually like to strip
attach.
or send-pr with attachment. Try to avoid send any
attachment to the mailing list, because attachments sent
to FreeBSD mailing lists are usually discarded by the
mailing list software.
<li>If a program produces a core dump, provide a stack
trace.
<li>If an application produces unexpected behaviour, provide
a clear and detailed description.
<li>If an application produces unexpected behaviour,
provide a clear and detailed description, including a
description of the behaviour that you were expecting.
</ul>
</li>
</ul>