| 1 |
commit: 71044ab300d054f295adfbda61112d8abc8e4368 |
| 2 |
Author: Sam James <sam <AT> gentoo <DOT> org> |
| 3 |
AuthorDate: Sat Jan 8 03:48:16 2022 +0000 |
| 4 |
Commit: Sam James <sam <AT> gentoo <DOT> org> |
| 5 |
CommitDate: Sat Jan 8 03:48:16 2022 +0000 |
| 6 |
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=71044ab3 |
| 7 |
|
| 8 |
README*: modernise a bit |
| 9 |
|
| 10 |
Signed-off-by: Sam James <sam <AT> gentoo.org> |
| 11 |
|
| 12 |
README | 5 +++-- |
| 13 |
README.Gentoo.patches | 12 ++++-------- |
| 14 |
2 files changed, 7 insertions(+), 10 deletions(-) |
| 15 |
|
| 16 |
diff --git a/README b/README |
| 17 |
index 12357f1..5a5d70b 100644 |
| 18 |
--- a/README |
| 19 |
+++ b/README |
| 20 |
@@ -16,8 +16,9 @@ Naming |
| 21 |
Documention |
| 22 |
----------- |
| 23 |
All patches need a header describing what the patch does, where it came from, |
| 24 |
-and all relevent URLs. Read http://dev.gentoo.org/~vapier/clean-patches and |
| 25 |
-in particular use scrub_patch() or face the wrath. |
| 26 |
+and all relevent URLs. Read https://dev.gentoo.org/~vapier/clean-patches (or |
| 27 |
+https://devmanual.gentoo.org/ebuild-writing/misc-files/patches/index.html#clean-patch-howto) |
| 28 |
+and in particular use scrub_patch() or face the wrath. |
| 29 |
|
| 30 |
Update README.history whenever you add (+), remove (-), or update (U) a patch. |
| 31 |
|
| 32 |
|
| 33 |
diff --git a/README.Gentoo.patches b/README.Gentoo.patches |
| 34 |
index 0463ad7..c6d3511 100644 |
| 35 |
--- a/README.Gentoo.patches |
| 36 |
+++ b/README.Gentoo.patches |
| 37 |
@@ -3,11 +3,11 @@ |
| 38 |
================ |
| 39 |
|
| 40 |
Gentoo patchsets that have grown too large to keep on the rsync mirrors have |
| 41 |
-been moved to our cvs tree. From there, we bundle up all the whee little |
| 42 |
+been moved to our git tree. From there, we bundle up all the wee little |
| 43 |
patches into a tarball and distribute it via our public mirroring system. |
| 44 |
|
| 45 |
If you want specific info about a patch (like wtf it does or whose great idea |
| 46 |
-it was to change the code), read the patch ! We try to fill out the top of |
| 47 |
+it was to change the code), read the patch! We try to fill out the top of |
| 48 |
them with useful info such as what it does, why it's needed, bug reports, |
| 49 |
original creators, etc. |
| 50 |
|
| 51 |
@@ -25,13 +25,9 @@ read-write git tree: git+ssh://git@××××××××××.org/proj/gcc-patches.git |
| 52 |
|
| 53 |
The patch naming/applying convention might be a little confusing to the Gentoo |
| 54 |
outsider, so here's a quick rundown. Patch tarballs are applied in Gentoo via |
| 55 |
-a helper command called "epatch". This command is pretty forgiving when it |
| 56 |
-comes to applying patches. |
| 57 |
+a helper command called "eapply". |
| 58 |
|
| 59 |
-For example, it will autodetect the required -p# by starting at 0 and counting |
| 60 |
-up until things apply. So do not expect a patch series to all be at the same -p |
| 61 |
-level even if they all apply from the same source directory. Typically however, |
| 62 |
-people will use -p0 or -p1. |
| 63 |
+Patches should use -p1. |
| 64 |
|
| 65 |
The epatch command will also use the -E option by default as the `patch` command |
| 66 |
can be pretty picky about removing files. We just force the issue. If you |
Archives