From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/
Date: Sat, 22 Jan 2022 23:40:57 +0000 (UTC) [thread overview]
Message-ID: <1642894854.e7c201902967728dffa91c9cca11c5896e15c98c.sam@gentoo> (raw)
commit: e7c201902967728dffa91c9cca11c5896e15c98c
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 22 23:39:42 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jan 22 23:40:54 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=e7c20190
ebuild-maintenance/new-ebuild: use .patch, not .diff
We almost always use .patch now, so let's just reference it here too.
Signed-off-by: Sam James <sam <AT> gentoo.org>
ebuild-maintenance/new-ebuild/text.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/ebuild-maintenance/new-ebuild/text.xml b/ebuild-maintenance/new-ebuild/text.xml
index 7ef8254..eebdb8d 100644
--- a/ebuild-maintenance/new-ebuild/text.xml
+++ b/ebuild-maintenance/new-ebuild/text.xml
@@ -101,8 +101,8 @@ this directory; any files bigger than 20KB-or-so should go to the
mirrors to lower the amount of (unneeded) files our users have to
download. You may want to consider naming patches you create yourself
just to get your package to build with a version-specific name, such
-as <c>mypkg-1.0-gentoo.diff</c>, or more
-simply, <c>1.0-gentoo.diff</c>. Also note that the
+as <c>mypkg-1.0-gentoo.patch</c>, or more
+simply, <c>1.0-gentoo.patch</c>. Also note that the
<c>gentoo</c> extension informs people that this patch was created
by us, the Gentoo Linux developers, rather than having been grabbed from a
mailing list or somewhere else. Again, you should not compress these
next reply other threads:[~2022-01-22 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 23:40 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-21 11:46 [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/ Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2020-03-02 10:49 Ulrich Müller
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=1642894854.e7c201902967728dffa91c9cca11c5896e15c98c.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