From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Thu, 14 Feb 2013 18:37:27 +0100 Subject: [Buildroot] [PATCH 6/9] manual: minor fix in patch-policy.txt In-Reply-To: <28331a810710249524be2ea3a286fff996ead804.1360795941.git.s.martin49@gmail.com> References: <28331a810710249524be2ea3a286fff996ead804.1360795941.git.s.martin49@gmail.com> Message-ID: <20130214183727.402fbb13@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Samuel Martin, On Wed, 13 Feb 2013 23:59:07 +0100, Samuel Martin wrote: > > Signed-off-by: Samuel Martin > --- > docs/manual/patch-policy.txt | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/docs/manual/patch-policy.txt b/docs/manual/patch-policy.txt > index 78ac5b6..468a954 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 > @@ -57,8 +57,8 @@ How patches are applied > 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. > + `-.patch.` (where ++ is the > + architecture name) are applied following the +ls+ command order. The -.patch. naming is deprecated, and I think should no longer be mentioned in the documentation. Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com