From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC] Revert "Added local directory as source of kernel code"
Date: Mon, 29 Aug 2016 09:16:38 +0200 [thread overview]
Message-ID: <20160829091638.1236158a@free-electrons.com> (raw)
In-Reply-To: <20160828214805.GE5758@free.fr>
Hello,
On Sun, 28 Aug 2016 23:48:05 +0200, Yann E. MORIN wrote:
> There are *always* users of any option we deprecate or remove.
>
> All we can do is make it easy for them to upgrade. Override-srcdir has
> been available for ages now (5 years in September), so it's not as if
> it were something new or complex to use.
The only major difference being that "override source dir" is meant to
be a "local" override, i.e something that developers do on their own
machine, for their own development. While the existing
BR2_LINUX_KERNEL_CUSTOM_LOCAL is really about having it as part of the
Buildroot configuration.
But nothing prevents people from having a version-controlled local.mk,
which makes it not-local anymore.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-29 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 22:34 [Buildroot] [PATCH RFC] Revert "Added local directory as source of kernel code" Yann E. MORIN
2016-08-27 20:23 ` Thomas Petazzoni
2016-08-27 22:54 ` Yann E. MORIN
2016-08-28 7:23 ` Thomas Petazzoni
2016-08-28 20:37 ` Peter Korsgaard
2016-08-28 21:48 ` Yann E. MORIN
2016-08-29 7:16 ` Thomas Petazzoni [this message]
2016-12-12 3:06 ` James Knight
2016-12-12 16:27 ` Thomas Petazzoni
2016-12-12 17:35 ` Yann E. MORIN
2016-12-12 17:52 ` Thomas Petazzoni
2016-12-12 22:31 ` James Knight
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=20160829091638.1236158a@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 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.