From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Naming convention for patches
Date: Thu, 2 Apr 2015 09:16:47 +0200 [thread overview]
Message-ID: <20150402091647.06db2ee5@free-electrons.com> (raw)
In-Reply-To: <CAJtjsKaG8QfL5ZHcZ7osJ0+T=eJTFgHxhCfqe=QWBDHa0z9q0w@mail.gmail.com>
Dear Johan Oudinet,
On Thu, 26 Mar 2015 17:57:43 +0100, Johan Oudinet wrote:
> In 9.8. Adding project-specific patches:
> "Otherwise, patch files matching <packagename>-*.patch are applied in
> alphabetical order."
>
> This naming convention has been changed in buildroot, so we can use
> the name provided by git format-patch (i.e., without prefixing it by
> the package name).
> Is this pattern still required for patches inside
> BR2_GLOBAL_PATCH_DIR, or is it simply a mistake from the
> documentation?
This is a mistake, and I've sent a patch that fixes it:
http://patchwork.ozlabs.org/patch/455879/
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-04-02 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 16:57 [Buildroot] Naming convention for patches Johan Oudinet
2015-04-02 7:16 ` Thomas Petazzoni [this message]
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=20150402091647.06db2ee5@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox