From: "Brian Evans" <grknight@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: tools-reference/diff-and-patch/
Date: Tue, 19 Mar 2019 18:28:34 +0000 (UTC) [thread overview]
Message-ID: <1553018940.f9fa8b3c19cb83e0ae12f18175c0d218fb30f343.grknight@gentoo> (raw)
commit: f9fa8b3c19cb83e0ae12f18175c0d218fb30f343
Author: Brian Evans <grknight <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 19 18:09:00 2019 +0000
Commit: Brian Evans <grknight <AT> gentoo <DOT> org>
CommitDate: Tue Mar 19 18:09:00 2019 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=f9fa8b3c
Mention eapply in diff and patch tools section
Closes: https://bugs.gentoo.org/652472
Signed-off-by: Brian Evans <grknight <AT> gentoo.org>
tools-reference/diff-and-patch/text.xml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools-reference/diff-and-patch/text.xml b/tools-reference/diff-and-patch/text.xml
index 0b3fd9c..01f1ad0 100644
--- a/tools-reference/diff-and-patch/text.xml
+++ b/tools-reference/diff-and-patch/text.xml
@@ -37,7 +37,8 @@ than <c>-u</c>.
To apply a patch, use <c>patch -pX < whatever.patch</c>,
where <c>X</c> is a number representing the number of path components
which must be removed (typically this is <c>0</c> or <c>1</c>). Within
-ebuilds, use the <c>epatch</c> function instead — see
+ebuilds, use the <c>epatch</c> function, or <c>eapply</c> function
+beginning with EAPI=6, instead — see
<uri link="::ebuild-writing/functions/src_prepare/epatch"/>.
</p>
next reply other threads:[~2019-03-19 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 18:28 Brian Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-21 8:36 [gentoo-commits] proj/devmanual:master commit in: tools-reference/diff-and-patch/ Ulrich Müller
2021-05-30 11:24 Ulrich Müller
2021-03-12 22:03 Ulrich Müller
2015-08-21 6:36 Justin Lecher
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=1553018940.f9fa8b3c19cb83e0ae12f18175c0d218fb30f343.grknight@gentoo \
--to=grknight@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