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

- Reword the FreeBSD-specific problem part, because many users can make that

Browse source 
kind of decision so we can help on this part. [1]
- We no longer suggest to send attach in mailing list, because the list
  usually like to strip it. Change the suggest with different choices to:

	*Put your attach in website.
	*copy-n-paste in http://freebsd-gnome.pastebin.com/
	*send-pr with attach

  Modify the FreeBSD GNOME FAQ and bug report are on the way too.

Discussed with:	marcus
Written by:	marcus [1]
This commit is contained in:
Jeremy Messenger 2006-01-06 22:20:05 +00:00
parent f84b036be7
commit 7189b7fa74
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=26789
1 changed files with 16 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
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.20 2005/10/04 20:06:58 hrs Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/bugging.sgml,v 1.21 2005/12/29 06:42:27 adamw Exp $">
<!ENTITY title "FreeBSD GNOME Project: Reporting a Bug">
<!ENTITY % navincludes SYSTEM "../includes.navgnome.sgml"> %navincludes;
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
@ -25,7 +25,11 @@
reported.
<li><b><i>After</i></b> deciding whether the problem is FreeBSD-specific,
or is a bug in an application that would affect all users,
on all operating systems.
on all operating systems. If you cannot determine if the
problem is FreeBSD-specific or not, then send your
problem to <a
href="mailto:&email;@FreeBSD.org">freebsd-gnome mailing
list</a>, and we can help decided where the problem lies.
</ul>
<h2>2. What to report?</h2>
@ -52,10 +56,16 @@
<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.
<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.
unsuccessful build by either upload in 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.
<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.
</ul>
</li>
</ul>