public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: bugzilla-howto.xml
Date: Sun, 28 Feb 2010 06:14:01 +0000	[thread overview]
Message-ID: <E1NlcPh-0002lG-Da@stork.gentoo.org> (raw)

nightmorph    10/02/28 06:14:01

  Modified:             bugzilla-howto.xml
  Log:
  update with new perl commands, bug 307147

Revision  Changes    Path
1.17                 xml/htdocs/doc/en/bugzilla-howto.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.17&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.17&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?r1=1.16&r2=1.17

Index: bugzilla-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- bugzilla-howto.xml	5 Mar 2009 12:13:20 -0000	1.16
+++ bugzilla-howto.xml	28 Feb 2010 06:14:00 -0000	1.17
@@ -1,8 +1,8 @@
 <?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.16 2009/03/05 12:13:20 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.17 2010/02/28 06:14:00 nightmorph Exp $ -->
 
-<guide link="/doc/en/bugzilla-howto.xml">
+<guide>
 <title>Gentoo Bug Reporting Guide</title>
 
 <author title="Author">
@@ -20,8 +20,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.14</version>
-<date>2009-03-05</date>
+<version>1.15</version>
+<date>2010-02-27</date>
 
 <chapter>
 <title>Introduction</title>
@@ -51,7 +51,7 @@
 </p>
 
 <pre caption="A run time error">
-$ <i>./bad_code `perl -e 'print Ax100'`</i>
+$ <i>./bad_code `perl -e 'print "A"x100'`</i>
 Segmentation fault
 </pre>
 
@@ -177,7 +177,7 @@
 </p>
 
 <pre caption="Breaking The Program">
-$ <i>./bad_code `perl -e 'print Ax100'`</i>
+$ <i>./bad_code `perl -e 'print "A"x100'`</i>
 Segmentation fault
 </pre>
 
@@ -189,7 +189,7 @@
 </p>
 
 <pre caption="Running Our Program Through GDB">
-$ <i>gdb --args ./bad_code `perl -e 'print Ax100'`</i>
+$ <i>gdb --args ./bad_code `perl -e 'print "A"x100'`</i>
 GNU gdb 6.3
 Copyright 2004 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you are






             reply	other threads:[~2010-02-28  6:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-28  6:14 Joshua Saddler (nightmorph) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-07-22 12:01 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: bugzilla-howto.xml Sven Vermeulen (swift)
2009-03-05 12:13 Jan Kundrat (jkt)
2009-03-05 12:02 Jan Kundrat (jkt)
2009-01-26  7:34 Joshua Saddler (nightmorph)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1NlcPh-0002lG-Da@stork.gentoo.org \
    --to=nightmorph@gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox