From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: profiles/use.mask/
Date: Wed, 7 Apr 2021 17:35:28 +0000 (UTC) [thread overview]
Message-ID: <1617816496.57db9ab1515d939818b85d73c4eca9397a2cd14d.ulm@gentoo> (raw)
commit: 57db9ab1515d939818b85d73c4eca9397a2cd14d
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 04:08:00 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Apr 7 17:28:16 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=57db9ab1
profiles/use.mask: use consistent <c> tags for arch names
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
profiles/use.mask/text.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/profiles/use.mask/text.xml b/profiles/use.mask/text.xml
index be6242f..8e3c3bc 100644
--- a/profiles/use.mask/text.xml
+++ b/profiles/use.mask/text.xml
@@ -11,9 +11,9 @@ particular profile. This can be useful for various reasons:
<ul>
<li>
- Masking hardware-specific feature flags. For example, <c>mmx</c> and <c>sse</c> are
- only available on x86, <c>altivec</c> is only available on <c>ppc</c> and <c>vis</c> is
- only available on sparc v9.
+ Masking hardware-specific feature flags. For example, <c>mmx</c> and
+ <c>sse</c> are only available on <c>x86</c>, <c>altivec</c> is only
+ available on <c>ppc</c> and <c>vis</c> is only available on <c>sparc</c> v9.
</li>
<li>
Disabling unavailable soft dependencies. A simple hypothetical example <d /> say
next reply other threads:[~2021-04-07 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 17:35 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-17 4:25 [gentoo-commits] proj/devmanual:master commit in: profiles/use.mask/ Sam James
2013-05-19 8:38 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=1617816496.57db9ab1515d939818b85d73c4eca9397a2cd14d.ulm@gentoo \
--to=ulm@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