From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id AF23313835A for ; Wed, 7 Apr 2021 17:35:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D7396E09F9; Wed, 7 Apr 2021 17:35:33 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AD2D9E09F9 for ; Wed, 7 Apr 2021 17:35:33 +0000 (UTC) Received: from oystercatcher.gentoo.org (unknown [IPv6:2a01:4f8:202:4333:225:90ff:fed9:fc84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 8F397335D75 for ; Wed, 7 Apr 2021 17:35:32 +0000 (UTC) Received: from localhost.localdomain (localhost [IPv6:::1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id A36E666A for ; Wed, 7 Apr 2021 17:35:28 +0000 (UTC) From: "Ulrich Müller" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Ulrich Müller" Message-ID: <1617816910.34957441bbcce538d388c262ec53b34d0d8ddcc5.ulm@gentoo> Subject: [gentoo-commits] proj/devmanual:master commit in: keywording/ X-VCS-Repository: proj/devmanual X-VCS-Files: keywording/text.xml X-VCS-Directories: keywording/ X-VCS-Committer: ulm X-VCS-Committer-Name: Ulrich Müller X-VCS-Revision: 34957441bbcce538d388c262ec53b34d0d8ddcc5 X-VCS-Branch: master Date: Wed, 7 Apr 2021 17:35:28 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: bdb7c8be-2edb-4541-a6d9-ab0ed4331af9 X-Archives-Hash: 8a09e1b81f754d7c6192af52c6624f87 commit: 34957441bbcce538d388c262ec53b34d0d8ddcc5 Author: Sam James gentoo org> AuthorDate: Sun Mar 21 05:25:39 2021 +0000 Commit: Ulrich Müller gentoo org> CommitDate: Wed Apr 7 17:35:10 2021 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=34957441 keywording: minor grammar/phrasing changes Signed-off-by: Sam James gentoo.org> Signed-off-by: Ulrich Müller gentoo.org> keywording/text.xml | 46 +++++++++++++++++++++++----------------------- 1 file changed, 23 insertions(+), 23 deletions(-) diff --git a/keywording/text.xml b/keywording/text.xml index 0f08c7e..fb490cc 100644 --- a/keywording/text.xml +++ b/keywording/text.xml @@ -168,20 +168,20 @@ archs (there is at least one case of a vim script which only worked on

-Note that most (non-x86) archs expect you to be on the arch team and bugzilla -alias if you are committing packages with keywords for that arch, and may have -additional requirements of which you should be aware (on mips, for example, -there are multiple ABIs and byte orders to consider a package working on your -o32 box may not work on o64 or n32). Contact the individual arch -teams for details. +Note that most (non-amd64/x86) archs expect you to be on the +arch team and bugzilla alias if you are committing packages with keywords for +that arch, and may have additional requirements of which you should be aware +(on mips, for example, there are multiple ABIs and byte orders to +consider a package working on your o32 box may not work on +o64 or n32). Contact the individual arch teams for details.

-It's important to note that alternative arches (like alpha, ia64, s390, sparc, -hppa, ppc*) are mainly undermanned arches, some of them are slow, they have -more basic problems and have a small userbase. Just file bugs for these -architectures when a package is going to be a dependency of a package already -keyworded. +It's important to note that alternative arches (like alpha, ia64, +s390, sparc, hppa, ppc*) are mainly understaffed +arches, some of them are slow, they have more basic problems and have a small +userbase. Just file bugs for these architectures when a package is going to be +a dependency of a package already keyworded.

@@ -253,8 +253,8 @@ teams to the CC list. They can do it manually, or they can fill the package list field, add the CC-ARCHES keyword, and let NATTkA automatically add arch teams to CC. -That way teams can remove themselves from the list when they are done, giving -a clear indication of which teams still have to stabilize a package. +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.

@@ -290,7 +290,7 @@ for further details):

For security fixes, the "reasonable amount of time" guideline may be relaxed. See the -Vulnerability Treatment Policy +Vulnerability Treatment Policy.

@@ -303,9 +303,9 @@ Vulnerability Treatment Policy AMD64, X86: If you are the maintainer of a package and own the respective amd64 or x86 hardware, you can do your own testing (stabilization and keywording) of your packages; as long as it is not a core system set dependency. Note that -it is acceptable to test x86 using a +it is acceptable to test x86 using a -specialized environment on amd64. +specialized environment on amd64.

@@ -321,15 +321,15 @@ the team can keep an eye out for possible keywording mistakes.

-Exotic architectures (like hppa, ia64, ppc*, sparc) are short on manpower, -so it's best if you avoid opening bugs for stabilization of new packages -for them, unless it is absolutely necessary (e.g., a reverse dependency -for your package). +Exotic architectures (like hppa, ia64, ppc*, sparc) +are short on help, so it's best if you avoid opening bugs for stabilization +of new packages for them, unless it is absolutely necessary (e.g., a reverse +dependency for your package).

-Some architectures (like mips, riscv) do not maintain a stable keyword. -So packages are not to be marked stable for one of these architectures. +Some architectures (like mips, riscv) do not maintain a stable +keyword, so packages are not to be marked stable for one of these architectures.

@@ -341,7 +341,7 @@ So packages are not to be marked stable for one of these architectures.

If you maintain an architecture-independent package (data files, icons, pure -Python, ...) then you may request that your package be stabilized on all arches +Python, ...), then you may request that your package be stabilized on all arches at once. To do this when you are filing the stabilization bug please add the keyword ALLARCHES in addition to STABLEREQ and CC the arches that you would like to stabilize.