[gentoo-doc-cvs] cvs commit: bugzilla-howto.xml

[Shyam Mani]

fox2mike    05/07/07 18:19:23

  Modified:    xml/htdocs/doc/en bugzilla-howto.xml
  Log:
  Fixed http -> https in a Bugzie link. Added a few <path> tags where needed.

Revision  Changes    Path
1.2       +23 -22    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.2&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.2&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.1&r2=1.2&cvsroot=gentoo

Index: bugzilla-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- bugzilla-howto.xml	7 Jul 2005 12:02:21 -0000	1.1
+++ bugzilla-howto.xml	7 Jul 2005 18:19:23 -0000	1.2
@@ -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.1 2005/07/07 12:02:21 fox2mike Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.2 2005/07/07 18:19:23 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.0</version>
+<version>1.1</version>
 <date>2005-07-07</date>
 
 <chapter>
@@ -364,8 +364,8 @@
 </pre>
 
 <p>
-This creates a file called strace.log in the current directory. We check the
-file, and shown below are the relevant parts from the file.
+This creates a file called <path>strace.log</path> in the current directory. We
+check the file, and shown below are the relevant parts from the file.
 </p>
 
 <pre caption="A Look At the strace Log">
@@ -378,7 +378,8 @@
 <path>.foobar2</path> instead of <path>.foobar</path>. We also see the program
 reading in "bar" as it should. In this case, we can recommend the ebuild
 maintainer to put a warning about it. For now though, we can copy over the
-config file from .foobar and modify it to produce the correct results. 
+config file from <path>.foobar</path> and modify it to produce the correct
+results. 
 </p>
 
 </body>
@@ -584,7 +585,7 @@
 
 <p>
 So to begin searching, we head over to the <uri
-link="http://bugs.gentoo.org/">Bugzilla Homepage</uri>.
+link="https://bugs.gentoo.org/">Bugzilla Homepage</uri>.
 </p>
 
 <figure link="/images/docs/bugzie-homepage.png" caption="Bugzilla Homepage"/>
@@ -964,24 +965,24 @@
 
 <ul>
   <li>
-	UNCONFIRMED - You're generally not going to see this too often. This
+  UNCONFIRMED - You're generally not going to see this too often. This
   means that a bug reporter has opened a bug using the advanced method and is
   uncertain his or her bug is an actual bug.
-	</li>
+  </li>
   <li>
-	NEW - Bugs that are first opened are considered new.
-	</li>
+  NEW - Bugs that are first opened are considered new.
+  </li>
   <li>
-	ASSIGNED - When the person you've assigned the bug too validates your
+  ASSIGNED - When the person you've assigned the bug too validates your
   bug, it will often receive ASSIGNED status while they figure out the issue.
   This let's you know that they've accepted your bug as a real bug.
-	</li>
+  </li>
   <li>
-	REOPENED - Someone has resolved a bug and you think the solution is not
+  REOPENED - Someone has resolved a bug and you think the solution is not
   feasible or the problem still persists. At this point, you may re-open the
   bug. However <b>please do not abuse this</b>. If a developer closes the bug a
   second or even third time, chances are that your bug is closed.
-	</li>
+  </li>
 </ul>
 
 <p>
@@ -1007,21 +1008,21 @@
 
 <ul>
   <li>
-	FIXED - The bug is fixed, follow the instructions to resolve your
+  FIXED - The bug is fixed, follow the instructions to resolve your
   issue.
-	</li>
+  </li>
   <li>
-	INVALID - You did not do something specifically documented, causing the
+  INVALID - You did not do something specifically documented, causing the
   bug
-	</li>
+  </li>
   <li>
-	DUPLICATE - You didn't use this guide and reported a duplicate bug
+  DUPLICATE - You didn't use this guide and reported a duplicate bug
   :)
-	</li>
+  </li>
   <li>
-	WORKSFORME - Developer/person assigned the bug cannot reproduce your
+  WORKSFORME - Developer/person assigned the bug cannot reproduce your
   error
-	</li>
+  </li>
 </ul>
 
 </body>



-- 
gentoo-doc-cvs@g.o mailing list