From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] mxs-bootlets: add support for custom patches
Date: Mon, 27 May 2013 13:42:49 -0300 [thread overview]
Message-ID: <51A38D09.3040201@zacarias.com.ar> (raw)
In-Reply-To: <519C6D64.8040109@mind.be>
On 05/22/2013 04:01 AM, Arnout Vandecappelle wrote:
>> Also, what about the existing *_CUSTOM_PATCH_DIR config options we have
>> for Linux, U-Boot, Barebox and a bunch of other boot/kernel packages?
>
> Here also I'm in favour of deprecating them.
>
> But probably it's better to start using the global patch dir now, and
> only start deprecating the old ways next year.
>
>
> Regards,
> Arnout
Ok, let's go for BR2_GLOBAL_PATCH_DIR, sent a V2 respinned.
Regards.
prev parent reply other threads:[~2013-05-27 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-18 19:25 [Buildroot] [PATCH 1/2] mxs-bootlets: add support for custom patches Gustavo Zacarias
2013-05-18 19:25 ` [Buildroot] [PATCH 2/2] configs: add sample for olimex mx233 olinuxino Gustavo Zacarias
2013-05-22 6:08 ` [Buildroot] [PATCH 1/2] mxs-bootlets: add support for custom patches Arnout Vandecappelle
2013-05-22 6:58 ` Thomas Petazzoni
2013-05-22 7:01 ` Arnout Vandecappelle
2013-05-27 16:42 ` Gustavo Zacarias [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=51A38D09.3040201@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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