| 1 |
swift 05/07/07 11:47:29 |
| 2 |
|
| 3 |
Modified: xml/htdocs/doc/en/draft bugzilla-howto.xml |
| 4 |
Log: |
| 5 |
Further spelling and grammar and language stuff |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.5 +10 -10 xml/htdocs/doc/en/draft/bugzilla-howto.xml |
| 9 |
|
| 10 |
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 |
| 11 |
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 |
| 12 |
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 |
| 13 |
|
| 14 |
Index: bugzilla-howto.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v |
| 17 |
retrieving revision 1.4 |
| 18 |
retrieving revision 1.5 |
| 19 |
diff -u -r1.4 -r1.5 |
| 20 |
--- bugzilla-howto.xml 7 Jul 2005 11:38:19 -0000 1.4 |
| 21 |
+++ bugzilla-howto.xml 7 Jul 2005 11:47:29 -0000 1.5 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v 1.4 2005/07/07 11:38:19 swift Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v 1.5 2005/07/07 11:47:29 swift Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/en/bugzilla-howto.xml"> |
| 29 |
<title>Gentoo Bug Reporting Guide</title> |
| 30 |
@@ -265,7 +265,7 @@ |
| 31 |
<p> |
| 32 |
This backtrace contains a large number of ?? marks. This is because without |
| 33 |
debug symbols, <c>gdb</c> doesn't know how the program was ran. Hence, it is |
| 34 |
-crucial that debug symbols are <e>not</e> stripped. Now remember awhile ago I |
| 35 |
+crucial that debug symbols are <e>not</e> stripped. Now remember a while ago I |
| 36 |
told you about the -g flag. Let's see what the output looks like with that: |
| 37 |
</p> |
| 38 |
|
| 39 |
@@ -485,8 +485,8 @@ |
| 40 |
<body> |
| 41 |
|
| 42 |
<p> |
| 43 |
-PORT_LOGDIR is a portage variable that sets up a log directory for individual emerge |
| 44 |
-logs. Let's take a look and see what that entails. First, run your emerge |
| 45 |
+PORT_LOGDIR is a portage variable that sets up a log directory for separate |
| 46 |
+emerge logs. Let's take a look and see what that entails. First, run your emerge |
| 47 |
with PORT_LOGDIR set to your favorite log location. Let's say we have a |
| 48 |
location /var/log/portage. We'll use that for our log directory: |
| 49 |
</p> |
| 50 |
@@ -536,7 +536,7 @@ |
| 51 |
|
| 52 |
<p> |
| 53 |
<uri link="http://www.bugzilla.org">Bugzilla</uri> is what we at Gentoo use to |
| 54 |
-handle bugs. Gentoo's Bugzilla is reachable by both HTTPS and HTTP. HTTPS is |
| 55 |
+handle bugs. Gentoo's Bugzilla is reachable by HTTPS and HTTP. HTTPS is |
| 56 |
available for those on insecure networks. For the sake of consistency, I will be |
| 57 |
using the HTTPS version in the examples to follow. Head over to <uri |
| 58 |
link="https://bugs.gentoo.org">Gentoo Bugs</uri> to see how it looks. |
| 59 |
@@ -777,11 +777,11 @@ |
| 60 |
If you were running SPARC, you would set it to SPARC. For this example, we know |
| 61 |
this error can occur on multiple architectures, so we'll select All. Operating |
| 62 |
System is what Operating System you're using. Because Gentoo is considered a |
| 63 |
-"Meta-distribution", it can run on other OSs besides Linux. Examples are |
| 64 |
-Gentoo on MacOS, Gentoo on FreeBSD, etc. For this example, we'll select All, as |
| 65 |
-this can occur on all types of systems. Build Identifier is what is being used |
| 66 |
-to report the bugs (for logging purposes).You can just leave this as is. Let's |
| 67 |
-see what we have so far: |
| 68 |
+"Meta-distribution", it can run on other operating systems beside Linux. |
| 69 |
+Examples are Gentoo on MacOS, Gentoo on FreeBSD, etc. For this example, |
| 70 |
+we'll select All, as this can occur on all types of systems. Build Identifier |
| 71 |
+is what is being used to report the bugs (for logging purposes). You can just |
| 72 |
+leave this as is. Let's see what we have so far: |
| 73 |
</p> |
| 74 |
|
| 75 |
<figure link="/images/docs/bugzie-basic-comp.png" caption="Completed Basic Information"/> |
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
-- |
| 80 |
gentoo-doc-cvs@g.o mailing list |
Archives