From: "Ulrich Müller" <ulm@gentoo.org>
To: <gentoo-pms@lists.gentoo.org>
Subject: [gentoo-pms] [PATCH] ebuild-vars.tex: Fix typo in IUSE description.
Date: Sat, 26 Nov 2016 11:21:09 +0100 [thread overview]
Message-ID: <22585.25109.534811.615555@a1i15.kph.uni-mainz.de> (raw)
---
ebuild-vars.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ebuild-vars.tex b/ebuild-vars.tex
index 996ad16..6c5a396 100644
--- a/ebuild-vars.tex
+++ b/ebuild-vars.tex
@@ -61,7 +61,7 @@ Ebuilds may define any of the following variables:
\item[IUSE] The \t{USE} flags used by the ebuild. Any eclass that works with \t{USE} flags must
also set \t{IUSE}, listing only the variables used by that eclass. The package manager is
responsible for merging these values. See section~\ref{sec:use-iuse-handling} for discussion on
- which values must be listed this variable.
+ which values must be listed in this variable.
\featurelabel{iuse-defaults} In EAPIs shown in table~\ref{tab:iuse-defaults-table} as supporting
\t{IUSE} defaults, any use flag name in \t{IUSE} may be prefixed by at most one of a plus or a
--
2.11.0.rc2
reply other threads:[~2016-11-26 10:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=22585.25109.534811.615555@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-pms@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