Gentoo Archives: gentoo-doc-cvs

From: Josh Saddler <nightmorph@××××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: bugzilla-howto.xml
Date: Sun, 01 Apr 2007 10:35:58
Message-Id: E1HXxPV-0007oQ-O6@stork.gentoo.org
1 nightmorph 07/04/01 10:35:45
2
3 Modified: bugzilla-howto.xml
4 Log:
5 added a smarter way to do attachments and info, thanks to jakub for the suggestion, bug 172975
6
7 Revision Changes Path
8 1.10 xml/htdocs/doc/en/bugzilla-howto.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.10&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?rev=1.10&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml?r1=1.9&r2=1.10
13
14 Index: bugzilla-howto.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v
17 retrieving revision 1.9
18 retrieving revision 1.10
19 diff -u -r1.9 -r1.10
20 --- bugzilla-howto.xml 14 Feb 2007 21:30:15 -0000 1.9
21 +++ bugzilla-howto.xml 1 Apr 2007 10:35:45 -0000 1.10
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/bugzilla-howto.xml,v 1.9 2007/02/14 21:30:15 nightmorph Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.10 2007/04/01 10:35:45 nightmorph Exp $ -->
27
28 <guide link="/doc/en/bugzilla-howto.xml">
29 <title>Gentoo Bug Reporting Guide</title>
30 @@ -20,8 +20,8 @@
31 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
32 <license/>
33
34 -<version>1.8</version>
35 -<date>2007-02-14</date>
36 +<version>1.9</version>
37 +<date>2007-04-01</date>
38
39 <chapter>
40 <title>Introduction</title>
41 @@ -848,9 +848,11 @@
42 is.
43 </li>
44 <li>
45 - URL is optional and is used to point to errors on a site someplace
46 - (pastebin, etc.). However, doing it inside the bug allows the developers be
47 - able to reference to it at any time and is preferred.
48 + URL is optional and is used to point to relevant information on another site
49 + (upstream bugzilla, release notes on package homepage etc.). You should
50 + never use URL to point to pastebins for error messages, logs, <c>emerge
51 + --info</c> output, screenshots or similar information. Instead, these should
52 + always be attached to the bug.
53 </li>
54 <li>
55 In the Summary, you should put the package category, name, and number.
56
57
58
59 --
60 gentoo-doc-cvs@g.o mailing list