fox2mike    05/07/10 14:13:08

  Modified:    xml/htdocs/doc/en bugzilla-howto.xml
  Log:
  Fixed gddb -> ggdb, which is correct.

Revision  Changes    Path
1.4       +4 -4      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.4&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.4&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.3&r2=1.4&cvsroot=gentoo

Index: bugzilla-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- bugzilla-howto.xml  9 Jul 2005 22:31:57 -0000       1.3
+++ bugzilla-howto.xml  10 Jul 2005 14:13:08 -0000      1.4
@@ -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.3 
2005/07/09 22:31:57 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.4 
2005/07/10 14:13:08 fox2mike Exp $ -->
 
 <guide link="/doc/en/bugzilla-howto.xml">
 <title>Gentoo Bug Reporting Guide</title>
@@ -20,7 +20,7 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.2</version>
+<version>1.3</version>
 <date>2005-07-10</date>
 
 <chapter>
@@ -132,7 +132,7 @@
 </p>
 
 <pre caption="make.conf settings">
-CFLAGS="-O2 -pipe -gddb3"
+CFLAGS="-O2 -pipe -ggdb3"
 CXXFLAGS="${CFLAGS}"
 </pre>
 
@@ -312,7 +312,7 @@
 <p>
 As you can see, -ggdb3 adds about <e>13178</e> 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. The backtrace, can 
be
+be worth it if presenting debug information to developers. The backtrace can be
 saved 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 simple, I recommend you read up on
 the documentation for gpm to see how to copy and paste with it). Now that we're



-- 
[email protected] mailing list

Reply via email to