aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSam James <sam@gentoo.org>2021-03-21 09:12:19 +0000
committerUlrich Müller <ulm@gentoo.org>2021-04-07 19:35:14 +0200
commit0b9aa967db85539baad1903c8c681a963e1765ec (patch)
tree961b3004ea481f207333efca5f3130ae805971e8 /keywording/text.xml
parentkeywording: add arm/arm64 policy for keywording/stablization (diff)
downloaddevmanual-0b9aa967db85539baad1903c8c681a963e1765ec.tar.gz
devmanual-0b9aa967db85539baad1903c8c681a963e1765ec.tar.bz2
devmanual-0b9aa967db85539baad1903c8c681a963e1765ec.zip
keywording: add QA policy link for dropped keywords
Signed-off-by: Sam James <sam@gentoo.org> Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Diffstat (limited to 'keywording/text.xml')
-rw-r--r--keywording/text.xml5
1 files changed, 3 insertions, 2 deletions
diff --git a/keywording/text.xml b/keywording/text.xml
index 9b71791..89ab1ea 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -215,8 +215,9 @@ architectures, then you should file a bug or ask on IRC before you upgrade the
ebuild. If you really need to get the ebuild added in a hurry, for example,
for a security fix, then you should drop any <c>KEYWORDS</c> which are causing
problems and CC the relevant architectures on the bug <d/> you <b>must</b> file
-a new bug to the architecture in question regarding this if no bug is already
-available.
+a <uri link="https://projects.gentoo.org/qa/policy-guide/keywords.html#pg0401">
+new bug</uri> to the architecture in question regarding this if no bug is
+already available.
</p>
<p>