From: | "Christian Faulhammer (fauli)" <fauli@g.o> |
---|---|
To: | gentoo-commits@l.g.o |
Subject: | [gentoo-commits] gentoo commit in xml/htdocs/proj/en/base/x86: arch-testers-faq.xml |
Date: | Fri, 08 Jan 2010 09:35:08 |
Message-Id: | E1NTBFI-0002xw-BL@stork.gentoo.org |
1 | fauli 10/01/08 09:35:04 |
2 | |
3 | Modified: arch-testers-faq.xml |
4 | Log: |
5 | AT FAQ: How to report |
6 | |
7 | Revision Changes Path |
8 | 1.15 xml/htdocs/proj/en/base/x86/arch-testers-faq.xml |
9 | |
10 | file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml?rev=1.15&view=markup |
11 | plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml?rev=1.15&content-type=text/plain |
12 | diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml?r1=1.14&r2=1.15 |
13 | |
14 | Index: arch-testers-faq.xml |
15 | =================================================================== |
16 | RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml,v |
17 | retrieving revision 1.14 |
18 | retrieving revision 1.15 |
19 | diff -u -r1.14 -r1.15 |
20 | --- arch-testers-faq.xml 8 Jan 2010 09:31:40 -0000 1.14 |
21 | +++ arch-testers-faq.xml 8 Jan 2010 09:35:03 -0000 1.15 |
22 | @@ -2,7 +2,7 @@ |
23 | |
24 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
25 | |
26 | -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml,v 1.14 2010/01/08 09:31:40 fauli Exp $ --> |
27 | +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/base/x86/arch-testers-faq.xml,v 1.15 2010/01/08 09:35:03 fauli Exp $ --> |
28 | |
29 | <guide link="/proj/en/base/x86/arch-testers-faq.xml"> |
30 | <title>Gentoo x86 Arch Tester's FAQ</title> |
31 | @@ -324,6 +324,12 @@ |
32 | reverse-dependencies are found in the <uri |
33 | link="http://tinderbox.dev.gentoo.org/misc/rindex/">rindex</uri>. |
34 | </li> |
35 | + <li> |
36 | + Inform the team about the successful test or the occured failures |
37 | + on the corresponding bug report including what you did and on |
38 | + what platform. If there were problems, add your <c>emerge |
39 | + --info</c> output, too. |
40 | + </li> |
41 | </ol> |
42 | |
43 | </body> |