From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/3] util-linux: rework utilities menu for finer control
Date: Sun, 12 Jul 2015 00:31:28 +0200 [thread overview]
Message-ID: <20150712003128.68c1964c@free-electrons.com> (raw)
In-Reply-To: <1436652601-2227-1-git-send-email-danomimanchego123@gmail.com>
Dear Danomi Manchego,
On Sat, 11 Jul 2015 18:09:58 -0400, Danomi Manchego wrote:
> This series changes the util-linux tool setup to support more scenarios.
Thanks. util-linux definitely needs some love. However, can you comment
on backward compatibility in terms of Config.in option? I.e, what
happens if a Buildroot user has an existing .config which uses
util-linux, and upgrades Buildroot to a version that contains your
patches. What will happen?
In any case, your patch 2/3 is removing
BR2_PACKAGE_UTIL_LINUX_BINARIES, so you should update Config.in.legacy
accordingly.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-11 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 22:09 [Buildroot] [PATCH v2 0/3] util-linux: rework utilities menu for finer control Danomi Manchego
2015-07-11 22:09 ` [Buildroot] [PATCH v2 1/3] util-linux: add more tool select options Danomi Manchego
2015-10-04 17:32 ` Thomas Petazzoni
2015-07-11 22:10 ` [Buildroot] [PATCH v2 2/3] util-linux: rework utilities menu for finer control Danomi Manchego
2015-07-11 22:10 ` [Buildroot] [PATCH v2 3/3] util-linux: put package options in a sub-menu Danomi Manchego
2015-07-11 22:31 ` Thomas Petazzoni [this message]
2015-07-12 1:15 ` [Buildroot] [PATCH v2 0/3] util-linux: rework utilities menu for finer control Danomi Manchego
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=20150712003128.68c1964c@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