1 |
fox2mike 05/07/07 18:19:23 |
2 |
|
3 |
Modified: xml/htdocs/doc/en bugzilla-howto.xml |
4 |
Log: |
5 |
Fixed http -> https in a Bugzie link. Added a few <path> tags where needed. |
6 |
|
7 |
Revision Changes Path |
8 |
1.2 +23 -22 xml/htdocs/doc/en/bugzilla-howto.xml |
9 |
|
10 |
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 |
11 |
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 |
12 |
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 |
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.1 |
18 |
retrieving revision 1.2 |
19 |
diff -u -r1.1 -r1.2 |
20 |
--- bugzilla-howto.xml 7 Jul 2005 12:02:21 -0000 1.1 |
21 |
+++ bugzilla-howto.xml 7 Jul 2005 18:19:23 -0000 1.2 |
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.1 2005/07/07 12:02:21 fox2mike Exp $ --> |
26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bugzilla-howto.xml,v 1.2 2005/07/07 18:19:23 fox2mike Exp $ --> |
27 |
|
28 |
<guide link="/doc/en/bugzilla-howto.xml"> |
29 |
<title>Gentoo Bug Reporting Guide</title> |
30 |
@@ -20,7 +20,7 @@ |
31 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
32 |
<license/> |
33 |
|
34 |
-<version>1.0</version> |
35 |
+<version>1.1</version> |
36 |
<date>2005-07-07</date> |
37 |
|
38 |
<chapter> |
39 |
@@ -364,8 +364,8 @@ |
40 |
</pre> |
41 |
|
42 |
<p> |
43 |
-This creates a file called strace.log in the current directory. We check the |
44 |
-file, and shown below are the relevant parts from the file. |
45 |
+This creates a file called <path>strace.log</path> in the current directory. We |
46 |
+check the file, and shown below are the relevant parts from the file. |
47 |
</p> |
48 |
|
49 |
<pre caption="A Look At the strace Log"> |
50 |
@@ -378,7 +378,8 @@ |
51 |
<path>.foobar2</path> instead of <path>.foobar</path>. We also see the program |
52 |
reading in "bar" as it should. In this case, we can recommend the ebuild |
53 |
maintainer to put a warning about it. For now though, we can copy over the |
54 |
-config file from .foobar and modify it to produce the correct results. |
55 |
+config file from <path>.foobar</path> and modify it to produce the correct |
56 |
+results. |
57 |
</p> |
58 |
|
59 |
</body> |
60 |
@@ -584,7 +585,7 @@ |
61 |
|
62 |
<p> |
63 |
So to begin searching, we head over to the <uri |
64 |
-link="http://bugs.gentoo.org/">Bugzilla Homepage</uri>. |
65 |
+link="https://bugs.gentoo.org/">Bugzilla Homepage</uri>. |
66 |
</p> |
67 |
|
68 |
<figure link="/images/docs/bugzie-homepage.png" caption="Bugzilla Homepage"/> |
69 |
@@ -964,24 +965,24 @@ |
70 |
|
71 |
<ul> |
72 |
<li> |
73 |
- UNCONFIRMED - You're generally not going to see this too often. This |
74 |
+ UNCONFIRMED - You're generally not going to see this too often. This |
75 |
means that a bug reporter has opened a bug using the advanced method and is |
76 |
uncertain his or her bug is an actual bug. |
77 |
- </li> |
78 |
+ </li> |
79 |
<li> |
80 |
- NEW - Bugs that are first opened are considered new. |
81 |
- </li> |
82 |
+ NEW - Bugs that are first opened are considered new. |
83 |
+ </li> |
84 |
<li> |
85 |
- ASSIGNED - When the person you've assigned the bug too validates your |
86 |
+ ASSIGNED - When the person you've assigned the bug too validates your |
87 |
bug, it will often receive ASSIGNED status while they figure out the issue. |
88 |
This let's you know that they've accepted your bug as a real bug. |
89 |
- </li> |
90 |
+ </li> |
91 |
<li> |
92 |
- REOPENED - Someone has resolved a bug and you think the solution is not |
93 |
+ REOPENED - Someone has resolved a bug and you think the solution is not |
94 |
feasible or the problem still persists. At this point, you may re-open the |
95 |
bug. However <b>please do not abuse this</b>. If a developer closes the bug a |
96 |
second or even third time, chances are that your bug is closed. |
97 |
- </li> |
98 |
+ </li> |
99 |
</ul> |
100 |
|
101 |
<p> |
102 |
@@ -1007,21 +1008,21 @@ |
103 |
|
104 |
<ul> |
105 |
<li> |
106 |
- FIXED - The bug is fixed, follow the instructions to resolve your |
107 |
+ FIXED - The bug is fixed, follow the instructions to resolve your |
108 |
issue. |
109 |
- </li> |
110 |
+ </li> |
111 |
<li> |
112 |
- INVALID - You did not do something specifically documented, causing the |
113 |
+ INVALID - You did not do something specifically documented, causing the |
114 |
bug |
115 |
- </li> |
116 |
+ </li> |
117 |
<li> |
118 |
- DUPLICATE - You didn't use this guide and reported a duplicate bug |
119 |
+ DUPLICATE - You didn't use this guide and reported a duplicate bug |
120 |
:) |
121 |
- </li> |
122 |
+ </li> |
123 |
<li> |
124 |
- WORKSFORME - Developer/person assigned the bug cannot reproduce your |
125 |
+ WORKSFORME - Developer/person assigned the bug cannot reproduce your |
126 |
error |
127 |
- </li> |
128 |
+ </li> |
129 |
</ul> |
130 |
|
131 |
</body> |
132 |
|
133 |
|
134 |
|
135 |
-- |
136 |
gentoo-doc-cvs@g.o mailing list |