nightmorph    07/04/01 10:35:45

  Modified:             bugzilla-howto.xml
  Log:
  added a smarter way to do attachments and info, thanks to jakub for the 
suggestion, bug 172975

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

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

Index: bugzilla-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- bugzilla-howto.xml  14 Feb 2007 21:30:15 -0000      1.9
+++ bugzilla-howto.xml  1 Apr 2007 10:35:45 -0000       1.10
@@ -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.9 
2007/02/14 21:30:15 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.10 
2007/04/01 10:35:45 nightmorph Exp $ -->
 
 <guide link="/doc/en/bugzilla-howto.xml">
 <title>Gentoo Bug Reporting Guide</title>
@@ -20,8 +20,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.8</version>
-<date>2007-02-14</date>
+<version>1.9</version>
+<date>2007-04-01</date>
 
 <chapter>
 <title>Introduction</title>
@@ -848,9 +848,11 @@
     is.
   </li>
   <li>
-    URL is optional and is used to point to errors on a site someplace
-    (pastebin, etc.). However, doing it inside the bug allows the developers be
-    able to reference to it at any time and is preferred.
+    URL is optional and is used to point to relevant information on another 
site
+    (upstream bugzilla, release notes on package homepage etc.). You should
+    never use URL to point to pastebins for error messages, logs, <c>emerge
+    --info</c> output, screenshots or similar information. Instead, these 
should
+    always be attached to the bug.
   </li>
   <li>
     In the Summary, you should put the package category, name, and number.



-- 
[email protected] mailing list

Reply via email to