| 1 |
commit: e7c201902967728dffa91c9cca11c5896e15c98c |
| 2 |
Author: Sam James <sam <AT> gentoo <DOT> org> |
| 3 |
AuthorDate: Sat Jan 22 23:39:42 2022 +0000 |
| 4 |
Commit: Sam James <sam <AT> gentoo <DOT> org> |
| 5 |
CommitDate: Sat Jan 22 23:40:54 2022 +0000 |
| 6 |
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=e7c20190 |
| 7 |
|
| 8 |
ebuild-maintenance/new-ebuild: use .patch, not .diff |
| 9 |
|
| 10 |
We almost always use .patch now, so let's just reference it here too. |
| 11 |
|
| 12 |
Signed-off-by: Sam James <sam <AT> gentoo.org> |
| 13 |
|
| 14 |
ebuild-maintenance/new-ebuild/text.xml | 4 ++-- |
| 15 |
1 file changed, 2 insertions(+), 2 deletions(-) |
| 16 |
|
| 17 |
diff --git a/ebuild-maintenance/new-ebuild/text.xml b/ebuild-maintenance/new-ebuild/text.xml |
| 18 |
index 7ef8254..eebdb8d 100644 |
| 19 |
--- a/ebuild-maintenance/new-ebuild/text.xml |
| 20 |
+++ b/ebuild-maintenance/new-ebuild/text.xml |
| 21 |
@@ -101,8 +101,8 @@ this directory; any files bigger than 20KB-or-so should go to the |
| 22 |
mirrors to lower the amount of (unneeded) files our users have to |
| 23 |
download. You may want to consider naming patches you create yourself |
| 24 |
just to get your package to build with a version-specific name, such |
| 25 |
-as <c>mypkg-1.0-gentoo.diff</c>, or more |
| 26 |
-simply, <c>1.0-gentoo.diff</c>. Also note that the |
| 27 |
+as <c>mypkg-1.0-gentoo.patch</c>, or more |
| 28 |
+simply, <c>1.0-gentoo.patch</c>. Also note that the |
| 29 |
<c>gentoo</c> extension informs people that this patch was created |
| 30 |
by us, the Gentoo Linux developers, rather than having been grabbed from a |
| 31 |
mailing list or somewhere else. Again, you should not compress these |
Archives