[gentoo-commits] proj/devmanual:master commit in: ebuild-writing/ebuild-maintenance/

["Markos Chandras" <hwoarang@gentoo.org>]

commit:     b092fa847e2af0993bc81d4d18918ecc2c6d6692
Author:     Manuel Rüger <mrueg <AT> rueg <DOT> eu>
AuthorDate: Thu Sep 26 03:19:45 2013 +0000
Commit:     Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Thu Sep 26 03:19:45 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=b092fa84

Add note about architectures that don't have a stable keyword.

---
 ebuild-writing/ebuild-maintenance/text.xml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/ebuild-writing/ebuild-maintenance/text.xml b/ebuild-writing/ebuild-maintenance/text.xml
index c228074..2959b50 100644
--- a/ebuild-writing/ebuild-maintenance/text.xml
+++ b/ebuild-writing/ebuild-maintenance/text.xml
@@ -233,9 +233,11 @@ the team can keep an eye out for possible keywording mistakes.
 </p>
 
 <p>
-Exotic architectures (like alpha, ia64, s390, sh, sparc, hppa, ppc*) are short on manpower, so it's best if you avoid opening stabilization bugs for them unless it is absolutely necessary (eg, a reverse dependency for your package). More about keywording policies can be found in the <uri link="::keywording">keywording</uri> section.
+Exotic architectures (like alpha, ia64, sparc, hppa, ppc*) are short on manpower, so it's best if you avoid opening stabilization bugs for them unless it is absolutely necessary (eg, a reverse dependency for your package). More about keywording policies can be found in the <uri link="::keywording">keywording</uri> section.
+</p>
+<p>
+Some architectures (like m68k, mips, s390, sh) do not maintain a stable keyword. So there is no use in marking a package stable for one of these architectures.
 </p>
-
 </body>
 </section>