From 58e2e9d8048907acda3fe14d03a6094a3dd05370 Mon Sep 17 00:00:00 2001 From: Samuel Martin Date: Wed, 13 Feb 2013 12:59:07 +0000 Subject: [PATCH] manual: minor fix in patch-policy.txt [Peter: Drop *.patch. description as noted by Thomas] Signed-off-by: Samuel Martin Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard --- docs/manual/patch-policy.txt | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/manual/patch-policy.txt b/docs/manual/patch-policy.txt index 78ac5b645a..14c6efc538 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 +-*.patch+. +These patch files should be named +-.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 `-*.patch` or - `-*.patch.` (where ++ is the architecture - name) are applied following the +ls+ command order. +* Otherwise, patch files matching `-*.patch` are applied + following the +ls+ command order. . Run the +_POST_PATCH_HOOKS+ commands if defined. -- 2.30.2