From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/autotools/
Date: Tue, 1 Mar 2022 09:59:09 +0000 (UTC) [thread overview]
Message-ID: <1646128736.6756801c7f1d3b8a6326567a164891333b1f10d3.sam@gentoo> (raw)
commit: 6756801c7f1d3b8a6326567a164891333b1f10d3
Author: Thomas Bracht Laumann Jespersen <t <AT> laumann <DOT> xyz>
AuthorDate: Thu Jan 27 09:39:43 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Mar 1 09:58:56 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=6756801c
general-concepts/autotools: Remove comment re einfo
In commit d9e28f40be32f76224ef0dbe2f3163e0615896f1, einfo lines were
removed from the examples but a paragraph still still referenced it.
Delete the paragraph.
Closes: https://bugs.gentoo.org/832156
Signed-off-by: Thomas Bracht Laumann Jespersen <t <AT> laumann.xyz>
Signed-off-by: Sam James <sam <AT> gentoo.org>
general-concepts/autotools/text.xml | 7 -------
1 file changed, 7 deletions(-)
diff --git a/general-concepts/autotools/text.xml b/general-concepts/autotools/text.xml
index 11cacf3..c4abdd4 100644
--- a/general-concepts/autotools/text.xml
+++ b/general-concepts/autotools/text.xml
@@ -141,13 +141,6 @@ src_configure() {
}
</codesample>
-<p>
-The <c>einfo</c> message before running autotools is not mandatory. However, these
-steps can sometimes take a while and may produce no output, so it may make sense
-to let the user know that something is still happening. See
-<uri link="::ebuild-writing/messages"/>.
-</p>
-
</body>
</section>
next reply other threads:[~2022-03-01 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 9:59 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-09 4:24 [gentoo-commits] proj/devmanual:master commit in: general-concepts/autotools/ Sam James
2020-01-27 19:58 Ulrich Müller
2018-06-14 18:43 Göktürk Yüksek
2014-01-21 17:09 Justin Lecher
2013-09-07 19:14 Markos Chandras
2013-09-07 18:46 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=1646128736.6756801c7f1d3b8a6326567a164891333b1f10d3.sam@gentoo \
--to=sam@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