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
