From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/misc-files/patches/
Date: Tue, 7 May 2024 17:22:03 +0000 (UTC) [thread overview]
Message-ID: <1715102212.5196ecf9214c74aec620b0b0580e6264083a184a.ulm@gentoo> (raw)
commit: 5196ecf9214c74aec620b0b0580e6264083a184a
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 29 16:19:17 2024 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue May 7 17:16:52 2024 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5196ecf9
ebuild-writing/misc-files/patches: Revert wording change
This is referred to as the "Clean patch howto" from several other
places. The wording change would also break links because the section
title is used as fragment identifier.
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
ebuild-writing/misc-files/patches/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ebuild-writing/misc-files/patches/text.xml b/ebuild-writing/misc-files/patches/text.xml
index c71551b..239fd1b 100644
--- a/ebuild-writing/misc-files/patches/text.xml
+++ b/ebuild-writing/misc-files/patches/text.xml
@@ -172,7 +172,7 @@ allows them to be applied unconditionally.
</section>
<section>
-<title>Clean patch guide</title>
+<title>Clean patch howto</title>
<body>
<p>
next reply other threads:[~2024-05-07 17:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 17:22 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-06 18:41 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/misc-files/patches/ Ulrich Müller
2021-06-18 6:13 Ulrich Müller
2021-06-18 6:13 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-02-22 16:51 Ulrich Müller
2021-02-20 8:00 Ulrich Müller
2018-06-22 18:40 Ulrich Müller
2016-06-16 1:19 Göktürk Yüksek
2015-08-21 6:36 Justin Lecher
2014-10-18 17:35 Markos Chandras
2014-07-24 18:06 ` 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=1715102212.5196ecf9214c74aec620b0b0580e6264083a184a.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