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

Add a line on running any build failure through gnomeloganalyzer.sh.

Browse source
This commit is contained in:
Joe Marcus Clarke 2004-06-06 20:29:46 +00:00
parent 334fc30615
commit 6b01bda32e
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=21112
1 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
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.14 2004/04/04 21:49:39 phantom Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/bugging.sgml,v 1.15 2004/04/05 02:14:09 adamw Exp $">
<!ENTITY title "FreeBSD GNOME Project: Reporting a Bug">
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -11,12 +11,15 @@
<h2>1. When should I make a bug report?</h2>
<ul>
<li><b><i>After</i></b> running any build failure
output through <a
href="/gnome/gnomeloganalyzer.sh">gnomeloganalyzer.sh</a>.
<li><b><i>After</i></b> running <tt>cvsup</tt> to obtain the most
recent ports tree.
<li><b><i>After</i></b> running <tt>portupgrade&nbsp;-a</tt> to ensure
that all applications are up-to-date.
<li><b><i>After</i></b> searching through the FreeBSD GNOME
<a href="http://www.FreeBSD.org/search/search.html">Mailing
<a href="http://lists.FreeBSD.org/pipermail/freebsd-gnome/">Mailing
list archives</a> to see if the problem has already been
reported.
<li><b><i>After</i></b> deciding whether the problem is FreeBSD-specific,