From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Added local directory as soure of kernel code
Date: Tue, 12 Feb 2013 22:45:54 +0100 [thread overview]
Message-ID: <20130212224554.40134349@skate> (raw)
In-Reply-To: <511A78BA.4010200@mind.be>
Dear Arnout Vandecappelle,
On Tue, 12 Feb 2013 18:15:38 +0100, Arnout Vandecappelle wrote:
> Looks like this is asked for over and over again, so I think it is
> really worth adding this option. I think this was in fact briefly
> discussed at the BR Developer Days but I didn't write it down in the
> report...
I think that I managed to be convinced that for packages for which we
already support a way of configuring the source location (from Git,
from a custom tarball, etc.), it makes sense to also offer an option to
set a local location, even if technically it is redundant with what
<foo>_OVERRIDE_SRCDIR is doing.
So I agree with the approach, as long as we limit it to a few key
packages like the Linux kernel and bootloaders.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-12 21:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 8:05 [Buildroot] [PATCH 1/1] Added local directory as soure of kernel code Rafal Fabich
2013-02-08 8:05 ` Rafal Fabich
2013-02-10 20:50 ` Yann E. MORIN
2013-02-11 8:30 ` Rafał Fabich
2013-02-12 17:15 ` Arnout Vandecappelle
2013-02-12 21:45 ` Thomas Petazzoni [this message]
2013-02-13 16:54 ` Rafał Fabich
2013-02-13 18:08 ` Yann E. MORIN
2013-02-21 18:28 ` Arnout Vandecappelle
2013-02-22 6:06 ` Rafał Fabich
2013-02-23 17:49 ` Arnout Vandecappelle
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=20130212224554.40134349@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.