From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: keywording/
Date: Mon, 27 Aug 2018 15:24:27 +0000 (UTC) [thread overview]
Message-ID: <1535383434.cd0550900d2461ceef2ad82da9371309a49131be.gokturk@gentoo> (raw)
commit: cd0550900d2461ceef2ad82da9371309a49131be
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 19 22:46:11 2018 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Mon Aug 27 15:23:54 2018 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=cd055090
keywording: sort keywords out
Closes: https://github.com/gentoo/devmanual.gentoo.org/pull/91
keywording/text.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 5ad2c75..1dfbc32 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -29,7 +29,7 @@ A sample <c>KEYWORDS</c> entry might look like:
</p>
<codesample lang="ebuild">
-KEYWORDS="x86 sparc ~mips ~ppc ~ppc-macos -ia64"
+KEYWORDS="-ia64 ~mips ~ppc sparc x86 ~ppc-macos"
</codesample>
<p>
@@ -82,15 +82,15 @@ The different levels of keyword are:
<p>
The <c>-*</c> keyword is special. It is used to indicate package versions which are
not worth trying to test on unlisted archs. For example, a binary-only package
-which is only supported upstream on <c>x86</c> and <c>ppc</c> might use:
+which is only supported upstream on <c>ppc</c> and <c>x86</c> might use:
</p>
<codesample lang="ebuild">
-KEYWORDS="-* x86 ppc"
+KEYWORDS="-* ppc x86"
</codesample>
<p>
-This is different in implication from <c>"x86 ppc"</c> <d /> the former implies that
+This is different in implication from <c>"ppc x86"</c> <d /> the former implies that
it will not work on other archs, whereas the latter implies that it has not been
tested.
</p>
next reply other threads:[~2018-08-27 15:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 15:24 Göktürk Yüksek [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-16 14:52 [gentoo-commits] proj/devmanual:master commit in: keywording/ Sam James
2022-03-14 17:07 Matt Turner
2022-03-10 23:33 Sam James
2022-02-18 18:19 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2021-10-13 13:42 Ulrich Müller
2021-10-13 13:42 Ulrich Müller
2021-07-16 9:11 Ulrich Müller
2021-07-03 16:21 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-11 13:16 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-15 7:21 Ulrich Müller
2020-07-12 18:32 Ulrich Müller
2020-05-06 7:49 Ulrich Müller
2020-01-25 6:02 Ulrich Müller
2020-01-23 13:50 Ulrich Müller
2015-06-17 12:05 Ulrich Müller
2015-03-14 9:20 Markos Chandras
2013-02-16 0:03 Markos Chandras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1535383434.cd0550900d2461ceef2ad82da9371309a49131be.gokturk@gentoo \
--to=gokturk@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox