From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: eclass-writing/
Date: Sat, 4 Sep 2021 10:33:06 +0000 (UTC) [thread overview]
Message-ID: <1630519330.ba6a05c97b16d9030ea437be37ebefa62358f6a6.ulm@gentoo> (raw)
commit: ba6a05c97b16d9030ea437be37ebefa62358f6a6
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Wed Sep 1 18:02:10 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Sep 1 18:02:10 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=ba6a05c9
eclass-writing: Fix dash
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
eclass-writing/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml
index a1f65a2..84599cb 100644
--- a/eclass-writing/text.xml
+++ b/eclass-writing/text.xml
@@ -789,7 +789,7 @@ jmake_src_compile() {
<p>
Sometimes an eclass is used incorrectly by an ebuild and the eclass
-knows it is being used incorrectly- the common example is an
+knows it is being used incorrectly <d/> the common example is an
eclass that only works with a specific set of EAPIs, but is being
accessed inherited by an ebuild with a different EAPI.
In those cases, used sparingly as a last resort, it is allowed
next reply other threads:[~2021-09-04 10:33 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 10:33 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-06 21:37 [gentoo-commits] proj/devmanual:master commit in: eclass-writing/ Ulrich Müller
2024-04-29 6:31 Ulrich Müller
2024-04-29 6:31 Ulrich Müller
2024-04-29 6:31 Ulrich Müller
2024-04-29 6:31 Ulrich Müller
2024-01-19 21:06 Ulrich Müller
2023-08-26 5:30 Ulrich Müller
2023-05-27 18:49 Ulrich Müller
2022-04-30 17:01 Ulrich Müller
2022-04-28 8:12 Ulrich Müller
2022-04-24 12:52 Ulrich Müller
2022-03-26 16:16 Ulrich Müller
2022-03-23 14:10 Ulrich Müller
2022-03-20 13:48 Ulrich Müller
2022-03-18 18:10 Sam James
2022-03-18 18:10 Sam James
2022-03-16 14:47 Sam James
2022-03-16 14:47 Sam James
2021-12-09 5:01 Sam James
2021-10-13 13:44 Ulrich Müller
2021-09-04 10:38 Ulrich Müller
2021-09-04 10:36 Ulrich Müller
2021-09-04 10:36 Ulrich Müller
2021-09-04 10:33 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-03-30 6:55 Ulrich Müller
2021-03-30 6:55 Ulrich Müller
2021-03-30 6:55 Ulrich Müller
2021-03-30 6:55 Ulrich Müller
2021-03-30 6:55 Ulrich Müller
2021-03-30 6:55 Ulrich Müller
2021-03-30 6:55 Ulrich Müller
2021-03-30 6:55 Ulrich Müller
2021-03-30 6:55 Ulrich Müller
2021-03-30 6:55 Ulrich Müller
2021-03-30 6:55 Ulrich Müller
2020-12-29 22:08 Göktürk Yüksek
2020-09-18 7:01 Ulrich Müller
2019-09-20 22:52 Göktürk Yüksek
2019-08-30 15:51 Göktürk Yüksek
2019-08-30 15:51 Göktürk Yüksek
2016-10-31 1:21 Göktürk Yüksek
2016-10-31 1:21 Göktürk Yüksek
2016-10-31 1:21 Göktürk Yüksek
2016-10-31 1:21 Göktürk Yüksek
2016-10-31 1:21 Göktürk Yüksek
2011-12-13 20:17 Petteri Räty
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=1630519330.ba6a05c97b16d9030ea437be37ebefa62358f6a6.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