All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/9] manual: minor fix in patch-policy.txt
Date: Thu, 14 Feb 2013 18:37:27 +0100	[thread overview]
Message-ID: <20130214183727.402fbb13@skate> (raw)
In-Reply-To: <28331a810710249524be2ea3a286fff996ead804.1360795941.git.s.martin49@gmail.com>

Dear Samuel Martin,

On Wed, 13 Feb 2013 23:59:07 +0100, Samuel Martin wrote:
> 
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
> ---
>  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 +<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
> @@ -57,8 +57,8 @@ How patches are applied
>    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.
> +  `<packagename>-<description>.patch.<arch>` (where +<arch>+ is the
> +  architecture name) are applied following the +ls+ command order.

The <packagename>-<description>.patch.<arch> 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

  parent reply	other threads:[~2013-02-14 17:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 22:59 [Buildroot] [pull request] Pull request for branch for-master/doc Samuel Martin
2013-02-13 22:59 ` [Buildroot] [PATCH 1/9] manual: cleanup and update editor tags Samuel Martin
2013-02-14  6:47   ` Arnout Vandecappelle
2013-02-17 21:50   ` Peter Korsgaard
2013-02-13 22:59 ` [Buildroot] [PATCH 2/9] manual: fix cross-refs Samuel Martin
2013-02-14  6:46   ` Arnout Vandecappelle
2013-02-13 22:59 ` [Buildroot] [PATCH 3/9] manual: sprinkle with some calls to MESSAGE Samuel Martin
2013-02-14  6:48   ` Arnout Vandecappelle
2013-02-17 21:51   ` Peter Korsgaard
2013-02-13 22:59 ` [Buildroot] [PATCH 4/9] manual: faq: add entry about the relocatable toolchain Samuel Martin
2013-02-14  6:49   ` Arnout Vandecappelle
2013-02-14 17:32   ` Thomas Petazzoni
2013-02-23 13:33     ` Samuel Martin
2013-02-13 22:59 ` [Buildroot] [PATCH 5/9] manual: faq: add workaround to avoid rebuilding the buildroot toolchain after each clean Samuel Martin
2013-02-14  7:04   ` Arnout Vandecappelle
2013-02-14 17:36   ` Thomas Petazzoni
2013-02-23 13:34     ` Samuel Martin
2013-02-13 22:59 ` [Buildroot] [PATCH 6/9] manual: minor fix in patch-policy.txt Samuel Martin
2013-02-14  7:06   ` Arnout Vandecappelle
2013-02-14 17:37   ` Thomas Petazzoni [this message]
2013-02-17 21:54   ` Peter Korsgaard
2013-02-13 22:59 ` [Buildroot] [PATCH 7/9] manual: misc. post-{build, image} scripts fixes Samuel Martin
2013-02-14  7:16   ` Arnout Vandecappelle
2013-02-13 22:59 ` [Buildroot] [PATCH 8/9] manual: update {deprecated, package}-list.txt Samuel Martin
2013-02-18  7:23   ` Arnout Vandecappelle
2013-02-25 21:22     ` Samuel Martin
2013-02-13 22:59 ` [Buildroot] [PATCH 9/9] Makefile: add to the release target a warning about the manual updates Samuel Martin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130214183727.402fbb13@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.