swift 05/07/07 11:47:29 Modified: xml/htdocs/doc/en/draft bugzilla-howto.xml Log: Further spelling and grammar and language stuff
Revision Changes Path 1.5 +10 -10 xml/htdocs/doc/en/draft/bugzilla-howto.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/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/draft/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/draft/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/draft/bugzilla-howto.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- bugzilla-howto.xml 7 Jul 2005 11:38:19 -0000 1.4 +++ bugzilla-howto.xml 7 Jul 2005 11:47:29 -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/draft/bugzilla-howto.xml,v 1.4 2005/07/07 11:38:19 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v 1.5 2005/07/07 11:47:29 swift Exp $ --> <guide link="/doc/en/bugzilla-howto.xml"> <title>Gentoo Bug Reporting Guide</title> @@ -265,7 +265,7 @@ <p> This backtrace contains a large number of ?? marks. This is because without debug symbols, <c>gdb</c> doesn't know how the program was ran. Hence, it is -crucial that debug symbols are <e>not</e> stripped. Now remember awhile ago I +crucial that debug symbols are <e>not</e> stripped. Now remember a while ago I told you about the -g flag. Let's see what the output looks like with that: </p> @@ -485,8 +485,8 @@ <body> <p> -PORT_LOGDIR is a portage variable that sets up a log directory for individual emerge -logs. Let's take a look and see what that entails. First, run your emerge +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 /var/log/portage. We'll use that for our log directory: </p> @@ -536,7 +536,7 @@ <p> <uri link="http://www.bugzilla.org";>Bugzilla</uri> is what we at Gentoo use to -handle bugs. Gentoo's Bugzilla is reachable by both HTTPS and HTTP. HTTPS is +handle bugs. Gentoo's Bugzilla is reachable by HTTPS and HTTP. HTTPS is available for those on insecure networks. For the sake of consistency, I will be using the HTTPS version in the examples to follow. Head over to <uri link="https://bugs.gentoo.org";>Gentoo Bugs</uri> to see how it looks. @@ -777,11 +777,11 @@ If you were running SPARC, you would set it to SPARC. For this example, we know this error can occur on multiple architectures, so we'll select All. Operating System is what Operating System you're using. Because Gentoo is considered a -"Meta-distribution", it can run on other OSs besides Linux. Examples are -Gentoo on MacOS, Gentoo on FreeBSD, etc. For this example, we'll select All, as -this can occur on all types of systems. Build Identifier is what is being used -to report the bugs (for logging purposes).You can just leave this as is. Let's -see what we have so far: +"Meta-distribution", it can run on other operating systems beside Linux. +Examples are Gentoo on MacOS, Gentoo on FreeBSD, etc. For this example, +we'll select All, as this can occur on all types of systems. Build Identifier +is what is being used to report the bugs (for logging purposes). You can just +leave this as is. Let's see what we have so far: </p> <figure link="/images/docs/bugzie-basic-comp.png" caption="Completed Basic Information"/> -- [email protected] mailing list
