Add a paragraph about searching the FreeBSD GNOME mailing list archives
before reporting a problem.
This commit is contained in:
parent
11ef433c12
commit
280eaac981
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=14290
1 changed files with 12 additions and 3 deletions
|
@ -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.6 2002/02/04 06:50:41 sobomax Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/gnome/docs/bugging.sgml,v 1.7 2002/08/25 19:54:28 marcus Exp $">
|
||||
<!ENTITY title "FreeBSD GNOME Project: Reporting a Bug">
|
||||
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
|
@ -56,8 +56,17 @@
|
|||
|
||||
<h2>2. Where to report?</h2>
|
||||
|
||||
<p>There are several ways to report a bug in GNOME running on a FreeBSD
|
||||
system: you could send a report to the
|
||||
<p>Before reporting a bug, or even sending an email to the list,
|
||||
<a href="http://www.freebsd.org/search/search.html">search</a>
|
||||
through the FreeBSD GNOME mailing list archives to see if this
|
||||
has already been reported. Most of the problems reported on
|
||||
the mailing list are repeats, and by searching you can find
|
||||
your solution much faster.
|
||||
</p>
|
||||
|
||||
<p>Once you are sure this is a new problem, there are several ways
|
||||
to report a bug in GNOME running on FreeBSD: you could
|
||||
send a report to the
|
||||
<a href="mailto:&email;@FreeBSD.org">freebsd-gnome mailing
|
||||
list</a>, file a problem report in the
|
||||
<a href="http://www.freebsd.org/support.html#gnats">FreeBSD bug
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue