Gentoo Archives: gentoo-commits

From: "Jorge Manuel B. S. Vicetto (jmbsvicetto)" <jmbsvicetto@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/desktop/kde: index.xml
Date: Mon, 01 Feb 2010 20:31:53
Message-Id: E1Nc2vl-0005aU-Qp@stork.gentoo.org
1 jmbsvicetto 10/02/01 20:31:33
2
3 Modified: index.xml
4 Log:
5 Rewrote part of the Reporting Bugs section.
6
7 Revision Changes Path
8 1.102 xml/htdocs/proj/en/desktop/kde/index.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/kde/index.xml?rev=1.102&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/kde/index.xml?rev=1.102&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/desktop/kde/index.xml?r1=1.101&r2=1.102
13
14 Index: index.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/desktop/kde/index.xml,v
17 retrieving revision 1.101
18 retrieving revision 1.102
19 diff -u -r1.101 -r1.102
20 --- index.xml 11 Jan 2010 05:12:06 -0000 1.101
21 +++ index.xml 1 Feb 2010 20:31:33 -0000 1.102
22 @@ -7,7 +7,7 @@
23 <name>KDE</name>
24 <longname>Gentoo KDE Project</longname>
25
26 -<date>2010-01-10</date>
27 +<date>2010-02-01</date>
28
29 <author title="Author">
30 <mail link="caleb"/>
31 @@ -369,10 +369,10 @@
32 <body>
33
34 <p>
35 -When you encounter a bug, this should always be reported. The best thing you
36 -could do is to check if it is already reported, and if not, report to the right
37 -people. When in doubt about the bug being a gentoo's fault or an upstream bug,
38 -this is the pattern that is usually used:
39 +When you encounter a bug, it should always be reported. The best thing you can
40 +do is to check whether it is already reported, and if not, report to the correct
41 +people. When in doubt about the bug being gentoo's fault or an upstream bug, try
42 +to follow this procedure:
43 </p>
44
45 <ul>
46 @@ -386,17 +386,17 @@
47 </li>
48 <li>
49 If the bug is a build failure, a depedency error or a general ebuild bug, it
50 - should reported to us.
51 + should reported to Gentoo.
52 </li>
53 <li>
54 - If you are still in doubt, we'd prefer a bug to us, so we can guide you
55 - then.
56 + If you are still in doubt, we'd prefer you open the bug for Gentoo, so we can
57 + check and advise you how to proceed.
58 </li>
59 </ul>
60
61 <note>
62 Before reporting the bug, make sure you have searched for similar bugs and
63 -that you haven't found your solution to the <uri
64 +that you haven't found your solution in the <uri
65 link="kde4-guide.xml#doc_chap4">Hints and Troubleshooting</uri> section of the guide
66 </note>