[Buildroot] [git commit] manual: minor fix in patch-policy.txt

Peter Korsgaard jacmet at sunsite.dk
Sun Feb 17 21:53:49 UTC 2013

commit: http://git.buildroot.net/buildroot/commit/?id=58e2e9d8048907acda3fe14d03a6094a3dd05370
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

[Peter: Drop *.patch.<arch> description as noted by Thomas]
Signed-off-by: Samuel Martin <s.martin49 at gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout at mind.be>
Signed-off-by: Peter Korsgaard <jacmet at sunsite.dk>
 docs/manual/patch-policy.txt |    7 +++----
 1 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/docs/manual/patch-policy.txt b/docs/manual/patch-policy.txt
index 78ac5b6..14c6efc 100644
--- a/docs/manual/patch-policy.txt
+++ b/docs/manual/patch-policy.txt
@@ -34,7 +34,7 @@ Most patches are provided within Buildroot, in the package
 directory; these typically aim to fix cross-compilation, libc support,
 or other such issues.
-These patch files should be named +<packagename>-*.patch+.
+These patch files should be named +<packagename>-<description>.patch+.
 A +series+ file, as used by +quilt+, may also be added in the
 package directory. In that case, the +series+ file defines the patch
@@ -56,9 +56,8 @@ How patches are applied
 * If a +series+ file exists in the package directory, then patches are
   applied according to the +series+ file;
-* Otherwise, patch files matching `<packagename>-*.patch` or
-  `<packagename>-*.patch.<arch>` (where +<arch>+ is the architecture
-  name) are applied following the +ls+ command order.
+* Otherwise, patch files matching `<packagename>-*.patch` are applied
+  following the +ls+ command order.
 . Run the +<packagename>_POST_PATCH_HOOKS+ commands if defined.

More information about the buildroot mailing list