aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSam James <sam@gentoo.org>2021-03-21 05:26:58 +0000
committerUlrich Müller <ulm@gentoo.org>2021-04-07 19:35:10 +0200
commit1f5f72e47dde3fae29ed9cd96ada00902cc9a395 (patch)
tree2a01bf11f3fb7431ded49effbee19bbf35956458 /keywording
parentkeywording: minor grammar/phrasing changes (diff)
downloaddevmanual-1f5f72e47dde3fae29ed9cd96ada00902cc9a395.tar.gz
devmanual-1f5f72e47dde3fae29ed9cd96ada00902cc9a395.tar.bz2
devmanual-1f5f72e47dde3fae29ed9cd96ada00902cc9a395.zip
keywording: make clear automatically CCing arches is preferred
Signed-off-by: Sam James <sam@gentoo.org> Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Diffstat (limited to 'keywording')
-rw-r--r--keywording/text.xml4
1 files 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>