From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/error-handling/
Date: Mon, 29 Mar 2021 20:44:04 +0000 (UTC) [thread overview]
Message-ID: <1617050496.56fe3529e0ae3d83bf5dc7e506345cbecf19ca0b.ulm@gentoo> (raw)
commit: 56fe3529e0ae3d83bf5dc7e506345cbecf19ca0b
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 20 09:26:05 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon Mar 29 20:41:36 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=56fe3529
ebuild-writing/error-handling: use eapply, not epatch
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
ebuild-writing/error-handling/text.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/ebuild-writing/error-handling/text.xml b/ebuild-writing/error-handling/text.xml
index 110f317..2e99f17 100644
--- a/ebuild-writing/error-handling/text.xml
+++ b/ebuild-writing/error-handling/text.xml
@@ -96,7 +96,7 @@ When using pipes, a subshell is introduced, so the following is unsafe:
</p>
<codesample lang="ebuild">
-cat list | while read file ; do epatch ${file} ; done
+cat list | while read file ; do eapply ${file} ; done
</codesample>
<p>
@@ -105,7 +105,7 @@ avoids this problem:
</p>
<codesample lang="ebuild">
-while read file ; do epatch ${file} ; done < list
+while read file ; do eapply ${file} ; done < list
</codesample>
</body>
next reply other threads:[~2021-03-29 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 20:44 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-28 19:35 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/error-handling/ Ulrich Müller
2024-09-28 19:35 Ulrich Müller
2021-03-21 5:48 Ulrich Müller
2019-12-02 21:33 Göktürk Yüksek
2017-05-06 22:49 Göktürk Yüksek
2013-05-10 22:55 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=1617050496.56fe3529e0ae3d83bf5dc7e506345cbecf19ca0b.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