From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] lxc needs gzip scripts for lxc-checkconfig runtime
Date: Sun, 20 Sep 2015 23:01:36 +0200 [thread overview]
Message-ID: <20150920230136.513b491c@free-electrons.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1509202012390.13941@orcam81.orcam.lan>
Jonathan,
On Sun, 20 Sep 2015 20:15:02 +0300 (IDT), Jonathan Ben Avraham wrote:
> I wondered whether to send a patch for each 'select' individually or to
> wait until I complete my testing and submit a single patch with all of the
> lxc selects. What do you prefer?
Both solutions are fine with me. You can send patches as you
progressively discover the issues, or send a single patch fixing all
problems at once.
I'm just wondering if we want to make all these dependencies actually
mandatory or not. It seems some of these dependencies are only used for
one specific tool in LXC. If the tool is not crucial in LXC usage,
maybe we should make it optional via a sub-option? I'm not sure here,
just thinking out loud.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-20 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-20 15:02 [Buildroot] [PATCH 1/1] lxc needs gzip scripts for lxc-checkconfig runtime Jonathan Ben-Avraham
2015-09-20 17:06 ` Thomas Petazzoni
2015-09-20 17:15 ` Jonathan Ben Avraham
2015-09-20 21:01 ` Thomas Petazzoni [this message]
2016-01-10 17:09 ` Yann E. MORIN
2016-01-11 6:32 ` Jonathan Ben Avraham
2016-01-11 18:13 ` Yann E. MORIN
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=20150920230136.513b491c@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