[gentoo-commits] gentoo commit in xml/htdocs/security/en: coordinator_guide.xml

[Alex Legler (a3li)]

a3li        09/10/30 10:31:52

  Modified:             coordinator_guide.xml
  Log:
  Improve wording for ebuild+ status

Revision  Changes    Path
1.25                 xml/htdocs/security/en/coordinator_guide.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/coordinator_guide.xml?rev=1.25&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/coordinator_guide.xml?rev=1.25&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/coordinator_guide.xml?r1=1.24&r2=1.25

Index: coordinator_guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/security/en/coordinator_guide.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- coordinator_guide.xml	1 Oct 2009 12:49:25 -0000	1.24
+++ coordinator_guide.xml	30 Oct 2009 10:31:52 -0000	1.25
@@ -437,11 +437,11 @@
 </p>
 
 <p>
-If the maintainer doesn't show up, we enter [ebuild+] status. In cases of fix
-version, you should test if a simple version bump (renaming the ebuild to the
-latest version and emerging it) works. In cases of patch, you should test if
-it applies cleanly. Then you should find a security bug wrangler with x86
-commit rights to do the bump and mark the ebuild ~ for testing.
+If the maintainer doesn't show up, we enter [ebuild+] status. In case a fixed
+version is available, you should test if a simple version bump (renaming the 
+ebuild to the version and emerging it) works. If only a patch is available, you
+should test if it applies cleanly. Then you should find a security bug wrangler
+with x86 commit rights to do the bump and mark the ebuild ~ for testing.
 </p>
 
 <p>