From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: tools-reference/diff-and-patch/
Date: Sun, 30 May 2021 11:24:32 +0000 (UTC) [thread overview]
Message-ID: <1622373762.6d4d7bf4a36fa3ff6bafda0ca0cef519c2663015.ulm@gentoo> (raw)
commit: 6d4d7bf4a36fa3ff6bafda0ca0cef519c2663015
Author: Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Sun May 30 07:59:09 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun May 30 11:22:42 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=6d4d7bf4
tools-reference/diff-and-patch/: add a link to "clean patches" page
- add a text link from tools-reference/diff-and-patch/index.html to
ebuild-writing/misc-files/patches
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <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 8a6172d..3be24db 100644
--- a/tools-reference/diff-and-patch/text.xml
+++ b/tools-reference/diff-and-patch/text.xml
@@ -30,7 +30,8 @@ format. This is generally the best format to use when sending patches
upstream too <d/> however, occasionally you may be asked to provide
context diffs, which are more portable than unifieds (but don't handle
conflicts as cleanly). In this case, use <c>-c</c> rather
-than <c>-u</c>.
+than <c>-u</c>. For a verbose guide into patches and patching, see
+<uri link="::ebuild-writing/misc-files/patches"/>.
</p>
<p>
next reply other threads:[~2021-05-30 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 11:24 Ulrich Müller [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-03-12 22:03 Ulrich Müller
2019-03-19 18:28 Brian Evans
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=1622373762.6d4d7bf4a36fa3ff6bafda0ca0cef519c2663015.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