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

From:	Sven Vermeulen <swift@×××××××××××.org>
To:	gentoo-doc-cvs@l.g.o
Subject:	[gentoo-doc-cvs] cvs commit: bugzilla-howto.xml
Date:	Thu, 07 Jul 2005 11:35:36
Message-Id:	`200507071134.j67BYPrp022660@robin.gentoo.org`

1

swift       05/07/07 11:35:16

2

3

  Modified:    xml/htdocs/doc/en/draft bugzilla-howto.xml

4

  Log:

5

  Spelling fixes, first run

6

7

Revision  Changes    Path

8

1.3       +13 -13    xml/htdocs/doc/en/draft/bugzilla-howto.xml

9

10

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo

11

plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo

12

diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo

13

14

Index: bugzilla-howto.xml

15

===================================================================

16

RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v

17

retrieving revision 1.2

18

retrieving revision 1.3

19

diff -u -r1.2 -r1.3

20

--- bugzilla-howto.xml	7 Jul 2005 11:24:54 -0000	1.2

21

+++ bugzilla-howto.xml	7 Jul 2005 11:35:16 -0000	1.3

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/draft/bugzilla-howto.xml,v 1.2 2005/07/07 11:24:54 fox2mike Exp $ -->

26

+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v 1.3 2005/07/07 11:35:16 swift Exp $ -->

27

28

 <guide link="/doc/en/bugzilla-howto.xml">

29

 <title>Gentoo Bug Reporting Guide</title>

30

@@ -280,7 +280,7 @@

31

 Here we see that a lot more information is available for developers. Not only is

32

 variable information displayed, but even the exact line numbers of the source

33

 files. This method is the most preferred if you can spare the extra space.

34

-Here's how much the filesize varies between debug, strip, and -g programs.

35

+Here's how much the file size varies between debug, strip, and -g programs.

36

 </p>

37

38

 <pre caption="Filesize differences With -g flag">

39

@@ -293,8 +293,8 @@

40

 </pre>

41

42

<p>

43

-As you can see, -g adds about a 1000 more bytes to the filesize over the one

44

-with debugging symbols. However, as shown above, this increase in filesize can

45

+As you can see, -g adds about a 1000 more bytes to the file size over the one

46

+with debugging symbols. However, as shown above, this increase in file size can

47

 be worth it if presenting debug information to developers. Now that we have

48

 obtained the backtrace, we can save it to a file by copying and pasting from the

49

 terminal (if it's a non-x based terminal, you can use gpm. To keep this doc

50

@@ -484,7 +484,7 @@

51

 <body>

52

53

<p>

54

-PORT_LOGDIR is a portage variable that sets up a logdir for individual emerge

55

+PORT_LOGDIR is a portage variable that sets up a log directory for individual emerge

56

 logs. Let's take a look and see what that entails. First, run your emerge

57

 with PORT_LOGDIR set to your favorite log location. Let's say we have a

58

 location /var/log/portage. We'll use that for our log directory:

59

@@ -535,9 +535,9 @@

60

61

<p>

62

 <uri link="http://www.bugzilla.org">Bugzilla</uri> is what we at Gentoo use to

63

-handle bugs. Gentoo's Bugzilla is accessible by both https and http. https is

64

+handle bugs. Gentoo's Bugzilla is accessible by both HTTPS and HTTP. HTTPS is

65

 available for those on insecure networks. For the sake of consistency, I will be

66

-using the https version in the examples to follow. Head over to <uri

67

+using the HTTPS version in the examples to follow. Head over to <uri

68

 link="https://bugs.gentoo.org">Gentoo Bugs</uri> to see how it looks.

69

 </p>

70

71

@@ -770,13 +770,13 @@

72

<p>

73

 First, there's the product. This is Gentoo Linux, which we selected earlier.

74

 Component is where the problem occurs. We use this to help us sort out the

75

-severity of the issue (ie. baselayout and core systems will be more important

76

+severity of the issue (i.e. baselayout and core systems will be more important

77

 than new ebuilds or application bugs). Here we select Application, as it is an

78

 application at fault. Hardware platform is what architecture you're running.

79

-If you were running sparc, you would set it to sparc. For this example, we know

80

+If you were running SPARC, you would set it to SPARC. For this example, we know

81

 this error can occur on multiple architectures, so we'll select All. Operating

82

 System is what Operating System you're using. Because Gentoo is considered a

83

-"Meta-distribution", it can run on other os's besides Linux. Examples are

84

+"Meta-distribution", it can run on other OSs besides Linux. Examples are

85

 Gentoo on MacOS, Gentoo on FreeBSD, etc. For this example, we'll select All, as

86

 this can occur on all types of systems. Build Identifier is what is being used

87

 to report the bugs (for logging purposes).You can just leave this as is. Let's

88

@@ -838,7 +838,7 @@

89

90

<p>

91

 Lastly we select the severity of the bug. Please look this over carefully. In

92

-most cases it's ok to leave it as is and someone will raise/lower it for you.

93

+most cases it's OK to leave it as is and someone will raise/lower it for you.

94

 However, if you raise the severity of the bug, please make sure you read it over

95

 carefully and make sure you're not making a mistake. Here we will set it to the

96

 default of normal:

97

@@ -931,7 +931,7 @@

98

 auto. In most cases it's best to manually set it. Our log file is a

99

 plain text file, so we select "plain text (text/plain)". Obsoletes are for when

100

 you are attaching a revision to a previously attached file. You can simply click

101

-a checkbox next to the old file and Bugzilla will cross it out in the bug,

102

+a check box next to the old file and Bugzilla will cross it out in the bug,

103

 indicating that the attachment has been obsoleted. Reassignment means you want

104

 to take the bug yourself. I rarely tend to use this.. and I don't think you will

105

 need to at some point (unless you create great patches and we don't care about

106

@@ -1003,7 +1003,7 @@

107

 <figure link="/images/docs/bugzie-options.png" caption="Bug Options"/>

108

109

<p>

110

-This gives you the option of Reopening the bug if you wish to (ie. the developer

111

+This gives you the option of Reopening the bug if you wish to (i.e. the developer

112

 thinks it's resolved but it's really not to your standards). Now our bug is

113

 fixed! However, different resolutions can occur. Here's a small list:

114

 </p>

--

119

gentoo-doc-cvs@g.o mailing list

1	swift 05/07/07 11:35:16
2
3	Modified: xml/htdocs/doc/en/draft bugzilla-howto.xml
4	Log:
5	Spelling fixes, first run
6
7	Revision Changes Path
8	1.3 +13 -13 xml/htdocs/doc/en/draft/bugzilla-howto.xml
9
10	file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo
11	plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo
12	diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/draft/bugzilla-howto.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo
13
14	Index: bugzilla-howto.xml
15	===================================================================
16	RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v
17	retrieving revision 1.2
18	retrieving revision 1.3
19	diff -u -r1.2 -r1.3
20	--- bugzilla-howto.xml 7 Jul 2005 11:24:54 -0000 1.2
21	+++ bugzilla-howto.xml 7 Jul 2005 11:35:16 -0000 1.3
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/draft/bugzilla-howto.xml,v 1.2 2005/07/07 11:24:54 fox2mike Exp $ -->
26	+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/draft/bugzilla-howto.xml,v 1.3 2005/07/07 11:35:16 swift Exp $ -->
27
28	<guide link="/doc/en/bugzilla-howto.xml">
29	<title>Gentoo Bug Reporting Guide</title>
30	@@ -280,7 +280,7 @@
31	Here we see that a lot more information is available for developers. Not only is
32	variable information displayed, but even the exact line numbers of the source
33	files. This method is the most preferred if you can spare the extra space.
34	-Here's how much the filesize varies between debug, strip, and -g programs.
35	+Here's how much the file size varies between debug, strip, and -g programs.
36	</p>
37
38	<pre caption="Filesize differences With -g flag">
39	@@ -293,8 +293,8 @@
40	</pre>
41
42	<p>
43	-As you can see, -g adds about a 1000 more bytes to the filesize over the one
44	-with debugging symbols. However, as shown above, this increase in filesize can
45	+As you can see, -g adds about a 1000 more bytes to the file size over the one
46	+with debugging symbols. However, as shown above, this increase in file size can
47	be worth it if presenting debug information to developers. Now that we have
48	obtained the backtrace, we can save it to a file by copying and pasting from the
49	terminal (if it's a non-x based terminal, you can use gpm. To keep this doc
50	@@ -484,7 +484,7 @@
51	<body>
52
53	<p>
54	-PORT_LOGDIR is a portage variable that sets up a logdir for individual emerge
55	+PORT_LOGDIR is a portage variable that sets up a log directory for individual emerge
56	logs. Let's take a look and see what that entails. First, run your emerge
57	with PORT_LOGDIR set to your favorite log location. Let's say we have a
58	location /var/log/portage. We'll use that for our log directory:
59	@@ -535,9 +535,9 @@
60
61	<p>
62	<uri link="http://www.bugzilla.org">Bugzilla</uri> is what we at Gentoo use to
63	-handle bugs. Gentoo's Bugzilla is accessible by both https and http. https is
64	+handle bugs. Gentoo's Bugzilla is accessible by both HTTPS and HTTP. HTTPS is
65	available for those on insecure networks. For the sake of consistency, I will be
66	-using the https version in the examples to follow. Head over to <uri
67	+using the HTTPS version in the examples to follow. Head over to <uri
68	link="https://bugs.gentoo.org">Gentoo Bugs</uri> to see how it looks.
69	</p>
70
71	@@ -770,13 +770,13 @@
72	<p>
73	First, there's the product. This is Gentoo Linux, which we selected earlier.
74	Component is where the problem occurs. We use this to help us sort out the
75	-severity of the issue (ie. baselayout and core systems will be more important
76	+severity of the issue (i.e. baselayout and core systems will be more important
77	than new ebuilds or application bugs). Here we select Application, as it is an
78	application at fault. Hardware platform is what architecture you're running.
79	-If you were running sparc, you would set it to sparc. For this example, we know
80	+If you were running SPARC, you would set it to SPARC. For this example, we know
81	this error can occur on multiple architectures, so we'll select All. Operating
82	System is what Operating System you're using. Because Gentoo is considered a
83	-"Meta-distribution", it can run on other os's besides Linux. Examples are
84	+"Meta-distribution", it can run on other OSs besides Linux. Examples are
85	Gentoo on MacOS, Gentoo on FreeBSD, etc. For this example, we'll select All, as
86	this can occur on all types of systems. Build Identifier is what is being used
87	to report the bugs (for logging purposes).You can just leave this as is. Let's
88	@@ -838,7 +838,7 @@
89
90	<p>
91	Lastly we select the severity of the bug. Please look this over carefully. In
92	-most cases it's ok to leave it as is and someone will raise/lower it for you.
93	+most cases it's OK to leave it as is and someone will raise/lower it for you.
94	However, if you raise the severity of the bug, please make sure you read it over
95	carefully and make sure you're not making a mistake. Here we will set it to the
96	default of normal:
97	@@ -931,7 +931,7 @@
98	auto. In most cases it's best to manually set it. Our log file is a
99	plain text file, so we select "plain text (text/plain)". Obsoletes are for when
100	you are attaching a revision to a previously attached file. You can simply click
101	-a checkbox next to the old file and Bugzilla will cross it out in the bug,
102	+a check box next to the old file and Bugzilla will cross it out in the bug,
103	indicating that the attachment has been obsoleted. Reassignment means you want
104	to take the bug yourself. I rarely tend to use this.. and I don't think you will
105	need to at some point (unless you create great patches and we don't care about
106	@@ -1003,7 +1003,7 @@
107	<figure link="/images/docs/bugzie-options.png" caption="Bug Options"/>
108
109	<p>
110	-This gives you the option of Reopening the bug if you wish to (ie. the developer
111	+This gives you the option of Reopening the bug if you wish to (i.e. the developer
112	thinks it's resolved but it's really not to your standards). Now our bug is
113	fixed! However, different resolutions can occur. Here's a small list:
114	</p>
115
116
117
118	--
119	gentoo-doc-cvs@g.o mailing list

Gentoo Archives: gentoo-doc-cvs