swift 05/07/07 11:35:16 Modified: xml/htdocs/doc/en/draft bugzilla-howto.xml Log: Spelling fixes, first run
Revision Changes Path 1.3 +13 -13 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.3&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.3&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.2&r2=1.3&cvsroot=gentoo Index: bugzilla-howto.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- bugzilla-howto.xml 7 Jul 2005 11:24:54 -0000 1.2 +++ bugzilla-howto.xml 7 Jul 2005 11:35:16 -0000 1.3 @@ -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.2 2005/07/07 11:24:54 fox2mike Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v 1.3 2005/07/07 11:35:16 swift Exp $ --> <guide link="/doc/en/bugzilla-howto.xml"> <title>Gentoo Bug Reporting Guide</title> @@ -280,7 +280,7 @@ Here we see that a lot more information is available for developers. Not only is variable information displayed, but even the exact line numbers of the source files. This method is the most preferred if you can spare the extra space. -Here's how much the filesize varies between debug, strip, and -g programs. +Here's how much the file size varies between debug, strip, and -g programs. </p> <pre caption="Filesize differences With -g flag"> @@ -293,8 +293,8 @@ </pre> <p> -As you can see, -g adds about a 1000 more bytes to the filesize over the one -with debugging symbols. However, as shown above, this increase in filesize can +As you can see, -g adds about a 1000 more bytes to the file size over the one +with debugging symbols. However, as shown above, this increase in file size can be worth it if presenting debug information to developers. Now that we have obtained the backtrace, we can save it to a file by copying and pasting from the terminal (if it's a non-x based terminal, you can use gpm. To keep this doc @@ -484,7 +484,7 @@ <body> <p> -PORT_LOGDIR is a portage variable that sets up a logdir for individual emerge +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 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: @@ -535,9 +535,9 @@ <p> <uri link="http://www.bugzilla.org";>Bugzilla</uri> is what we at Gentoo use to -handle bugs. Gentoo's Bugzilla is accessible by both https and http. https is +handle bugs. Gentoo's Bugzilla is accessible by both 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 +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. </p> @@ -770,13 +770,13 @@ <p> First, there's the product. This is Gentoo Linux, which we selected earlier. Component is where the problem occurs. We use this to help us sort out the -severity of the issue (ie. baselayout and core systems will be more important +severity of the issue (i.e. baselayout and core systems will be more important than new ebuilds or application bugs). Here we select Application, as it is an application at fault. Hardware platform is what architecture you're running. -If you were running sparc, you would set it to sparc. For this example, we know +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 os's besides Linux. Examples are +"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 @@ -838,7 +838,7 @@ <p> Lastly we select the severity of the bug. Please look this over carefully. In -most cases it's ok to leave it as is and someone will raise/lower it for you. +most cases it's OK to leave it as is and someone will raise/lower it for you. However, if you raise the severity of the bug, please make sure you read it over carefully and make sure you're not making a mistake. Here we will set it to the default of normal: @@ -931,7 +931,7 @@ auto. In most cases it's best to manually set it. Our log file is a plain text file, so we select "plain text (text/plain)". Obsoletes are for when you are attaching a revision to a previously attached file. You can simply click -a checkbox next to the old file and Bugzilla will cross it out in the bug, +a check box next to the old file and Bugzilla will cross it out in the bug, indicating that the attachment has been obsoleted. Reassignment means you want to take the bug yourself. I rarely tend to use this.. and I don't think you will need to at some point (unless you create great patches and we don't care about @@ -1003,7 +1003,7 @@ <figure link="/images/docs/bugzie-options.png" caption="Bug Options"/> <p> -This gives you the option of Reopening the bug if you wish to (ie. the developer +This gives you the option of Reopening the bug if you wish to (i.e. the developer thinks it's resolved but it's really not to your standards). Now our bug is fixed! However, different resolutions can occur. Here's a small list: </p> -- [email protected] mailing list
