From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 5 RFC] uclibc/busybox: fix handling of configuration file
Date: Sun, 29 Jun 2014 12:05:49 +0200 [thread overview]
Message-ID: <53AFE4FD.5080707@mind.be> (raw)
In-Reply-To: <20140629102012.33364d0e@free-electrons.com>
On 29/06/14 10:20, Thomas Petazzoni wrote:
> Dear Thomas De Schampheleire,
>
> On Sun, 29 Jun 2014 10:13:28 +0200, Thomas De Schampheleire wrote:
>
>>> This sounds like a very interesting idea, I'll explore it further in
>>> the context of this patch series.
>>
>> I'm working on this now, but I wonder which is the right approach wrt
>> the organization of the patch series:
>>
>> - first line up linux, busybox, uclibc in the way they handle the
>> kconfig stuff, then extract this to a kconfig-package framework
>> - or first introduce a kconfig-package framework with the 'right'
>> handling, then convert each of linux, busybox, uclibc in subsequent
>> patches?
>
> I'd say it doesn't matter that much. Maybe the first one allows more
> easily to see the functional changes that are made, by really I don't
> think it matter. At least on my end, I'd be happy with any of those two
> solutions.
Same here. I had thought about it and found arguments for both options, so I
thought it better not to say anything :-)
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2014-06-29 10:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 13:45 [Buildroot] [PATCH 0 of 5 RFC] uclibc/busybox: fix handling of configuration file Thomas De Schampheleire
2014-06-22 13:45 ` [Buildroot] [PATCH 1 of 5 RFC] uclibc: menuconfig: take into account initial settings from config file Thomas De Schampheleire
2014-06-22 14:05 ` Yann E. MORIN
2014-06-22 16:52 ` Thomas Petazzoni
2014-06-22 17:23 ` Thomas De Schampheleire
2014-06-22 17:29 ` Danomi Manchego
2014-06-22 18:52 ` Thomas De Schampheleire
2014-06-22 19:07 ` Danomi Manchego
2014-06-24 18:35 ` Thomas De Schampheleire
2014-06-25 6:16 ` Arnout Vandecappelle
2014-06-30 19:31 ` Thomas De Schampheleire
2014-07-01 6:09 ` Arnout Vandecappelle
2014-07-01 8:35 ` Thomas De Schampheleire
2014-06-22 13:45 ` [Buildroot] [PATCH 2 of 5 RFC] uclibc: update-config: preserve freshly configured settings Thomas De Schampheleire
2014-06-22 14:07 ` Yann E. MORIN
2014-06-22 13:45 ` [Buildroot] [PATCH 3 of 5 RFC] busybox: fix typo overwritting Thomas De Schampheleire
2014-06-22 13:57 ` Yann E. MORIN
2014-06-22 13:45 ` [Buildroot] [PATCH 4 of 5 RFC] busybox: menuconfig: take into account initial settings from config file Thomas De Schampheleire
2014-06-22 14:10 ` Yann E. MORIN
2014-06-22 13:45 ` [Buildroot] [PATCH 5 of 5 RFC] busybox: update-config: preserve freshly configured settings Thomas De Schampheleire
2014-06-22 14:14 ` Yann E. MORIN
2014-06-22 14:22 ` Thomas De Schampheleire
2014-06-22 14:46 ` Yann E. MORIN
2014-06-25 6:06 ` [Buildroot] [PATCH 0 of 5 RFC] uclibc/busybox: fix handling of configuration file Arnout Vandecappelle
2014-06-25 19:24 ` Thomas De Schampheleire
2014-06-29 8:13 ` Thomas De Schampheleire
2014-06-29 8:20 ` Thomas Petazzoni
2014-06-29 10:05 ` Arnout Vandecappelle [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=53AFE4FD.5080707@mind.be \
--to=arnout@mind.be \
--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.