[gentoo-commits] proj/devmanual:master commit in: keywording/

["Ulrich Müller" <ulm@gentoo.org>]

commit:     1f5f72e47dde3fae29ed9cd96ada00902cc9a395
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 05:26:58 2021 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr  7 17:35:10 2021 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=1f5f72e4

keywording: make clear automatically CCing arches is preferred

Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 keywording/text.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/keywording/text.xml b/keywording/text.xml
index fb490cc..ea28bed 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -249,10 +249,10 @@ In order to request stabilization of an ebuild, file a bug to the package's
 maintainer (which may be yourself) in the Stabilization component, and list
 all secondary maintainers in the bug's CC. When the maintainers consider the
 ebuild to be ready for stabilization, they will add the relevant architecture
-teams to the CC list. They can do it manually, or they can fill the package
+teams to the CC list. They can fill the package
 list field, add the <c>CC-ARCHES</c> keyword, and let
 <uri link="https://dev.gentoo.org/~mgorny/doc/nattka/">NATTkA</uri>
-automatically add arch teams to CC.
+automatically add arch teams to CC (preferred), or do this manually.
 That way, teams can remove themselves from the list when they are done, giving
 a clear indication of which teams still remain to stabilize a package.
 </p>