neysx 05/07/22 23:46:11 Modified: xml/htdocs/doc/en bugzilla-howto.xml Log: Done some coding style/link fixing
Revision Changes Path 1.5 +131 -146 xml/htdocs/doc/en/bugzilla-howto.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.5&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.5&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/bugzilla-howto.xml.diff?r1=1.4&r2=1.5&cvsroot=gentoo Index: bugzilla-howto.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- bugzilla-howto.xml 10 Jul 2005 14:13:08 -0000 1.4 +++ bugzilla-howto.xml 22 Jul 2005 23:46:11 -0000 1.5 @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.4 2005/07/10 14:13:08 fox2mike Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.5 2005/07/22 23:46:11 neysx Exp $ --> <guide link="/doc/en/bugzilla-howto.xml"> <title>Gentoo Bug Reporting Guide</title> @@ -20,8 +20,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>1.3</version> -<date>2005-07-10</date> +<version>1.4</version> +<date>2005-07-22</date> <chapter> <title>Introduction</title> @@ -86,11 +86,11 @@ </pre> <p> -These errors can be quite troublesome. However, once you find them, what do -you do? The following sections will look at two important tools for handling -run time errors. After that, we'll take a look at compile errors, and how to -handle them. Let's start out with the first tool for debugging run time -errors -- <c>gdb</c>. +These errors can be quite troublesome. However, once you find them, what do you +do? The following sections will look at two important tools for handling run +time errors. After that, we'll take a look at compile errors, and how to handle +them. Let's start out with the first tool for debugging run time errors -- +<c>gdb</c>. </p> </body> @@ -111,7 +111,7 @@ program is to <c>emerge</c> the program with <c>FEATURES="nostrip"</c>. This prevents the stripping of debug symbols. Why are programs stripped by default? The reason is the same as that for having gzipped man pages -- saving space. -Here's how the size of a program varies with and without debug symbol stripping. +Here's how the size of a program varies with and without debug symbol stripping. </p> <pre caption="Filesize Comparison"> @@ -128,7 +128,7 @@ the size! Two more things can be done for debugging. The first is adding ggdb3 to your CFLAGS and CXXFLAGS. This flag adds more debugging information than is generally included. We'll see what that means later on. This is how -<path>/etc/make.conf</path> <e>might</e> look with the newly added flags. +<path>/etc/make.conf</path> <e>might</e> look with the newly added flags. </p> <pre caption="make.conf settings"> @@ -137,9 +137,9 @@ </pre> <p> -Lastly, you can also add debug to the package's USE flags. This can be done with the -<path>package.use</path> file. -</p> +Lastly, you can also add debug to the package's USE flags. This can be done +with the <path>package.use</path> file. +</p> <pre caption="Using package.use to add debug USE flag"> # <i>echo "category/package debug" >> /etc/portage/package.use</i> @@ -395,7 +395,7 @@ reading in "bar" as it should. In this case, we can recommend the ebuild maintainer to put a warning about it. For now though, we can copy over the config file from <path>.foobar</path> and modify it to produce the correct -results. +results. </p> </body> @@ -510,9 +510,9 @@ <body> <p> -PORT_LOGDIR is a portage variable that sets up a log directory for separate -emerge logs. Let's take a look and see what that entails. First, run your emerge -with PORT_LOGDIR set to your favorite log location. Let's say we have a +PORT_LOGDIR is a portage variable that sets up a log directory for separate +emerge logs. Let's take a look and see what that entails. First, run your +emerge with PORT_LOGDIR set to your favorite log location. Let's say we have a location <path>/var/log/portage</path>. We'll use that for our log directory: </p> @@ -639,7 +639,7 @@ <p> This is how the Advanced Search Page looks like. While it may seem overwhelming at first, we're going to look at a few simple areas to narrow down the rather -vague searches bugzilla returns. +vague searches bugzilla returns. </p> <figure link="/images/docs/bugzie-content.png" caption="Content"/> @@ -759,15 +759,13 @@ <p> Another common misconception occurs with our Documentation bugs. For example, a -user finds a bug with the <uri -link="http://www.gentoo.org/proj/en/releng/catalyst/index.xml";>Catalyst +user finds a bug with the <uri link="/proj/en/releng/catalyst/">Catalyst Docs</uri>. The general tendency is to file a bug under Docs-user, which gets assigned to the <uri link="http://gdp.gentoo.org";>GDP</uri>, when it should -actually go to a member of the <uri -link="http://www.gentoo.org/proj/en/releng/";>Release Engineering</uri> team. As -a rule of thumb, only documentation under http://www.gentoo.org/doc/* is under -the GDP. Anything under http://www.gentoo.org/proj/* is under the respective -teams. +actually go to a member of the <uri link="/proj/en/releng/">Release +Engineering</uri> team. As a rule of thumb, only documentation under +<path>http://www.gentoo.org/doc/*</path> is under the GDP. Anything under +<path>http://www.gentoo.org/proj/*</path> is under the respective teams. </p> <note> @@ -779,8 +777,9 @@ </note> <p> -Our bug goes in Gentoo Linux as it's an ebuild bug. We head over there and are presented -with the multi-step bug reporting process. Let us now proceed with Step 1... +Our bug goes in Gentoo Linux as it's an ebuild bug. We head over there and are +presented with the multi-step bug reporting process. Let us now proceed with +Step 1... </p> <figure link="/images/docs/bugzie-guide-step1.png" caption="Guided Format Step 1"/> @@ -808,22 +807,23 @@ <ul> <li> - First, there's the Product. The product will narrow down the bug to a - specific area of Gentoo like Bugzilla (for bugs relating to bugs.gentoo.org), - Docs-user(for User Documentation) or Gentoo Linux (for ebuilds and the like). + First, there's the Product. The product will narrow down the bug to a + specific area of Gentoo like Bugzilla (for bugs relating to + bugs.gentoo.org), Docs-user(for User Documentation) or Gentoo Linux (for + ebuilds and the like). </li> <li> - Component is where exactly the problem occurs, more specifically which part - of selected product the bug comes under. This makes classification easier. + Component is where exactly the problem occurs, more specifically which part + of selected product the bug comes under. This makes classification easier. </li> <li> - Hardware platform is what architecture you're running. If you were running - SPARC, you would set it to SPARC. + Hardware platform is what architecture you're running. If you were running + SPARC, you would set it to SPARC. </li> <li> - Operating System is what Operating System you're using. Because Gentoo is - considered a "Meta-distribution", it can run on other operating systems - beside Linux. + Operating System is what Operating System you're using. Because Gentoo is + considered a "Meta-distribution", it can run on other operating systems + beside Linux. </li> </ul> @@ -832,34 +832,27 @@ </p> <ul> - <li> - Product - Gentoo Linux (Since it is an ebuild issue) - </li> - <li> - Component - Application (It is an application at fault, foobar2) - </li> - <li> - Hardware Platform - All (This error could occur across architectures) - </li> - <li> - Operation System - All (It could occur on all types of systems) - </li> + <li>Product - Gentoo Linux (Since it is an ebuild issue)</li> + <li>Component - Application (It is an application at fault, foobar2)</li> + <li>Hardware Platform - All (This error could occur across architectures)</li> + <li>Operation System - All (It could occur on all types of systems)</li> </ul> <figure link="/images/docs/bugzie-basic-comp.png" caption="Completed Basic Information"/> <ul> <li> -- [email protected] mailing list
