From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master] buildroot; move defconfigs to configs/ and print in help
Date: Mon, 05 Oct 2009 09:09:29 +0200 [thread overview]
Message-ID: <873a5y5nbq.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20091005084845.023ff120@surf> (Thomas Petazzoni's message of "Mon\, 5 Oct 2009 08\:48\:45 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> As discussed earlier on the mailing list. It simplifies code, gives
>> more sensible error message on typos and makes the defconfigs easier
>> to find for users.
Thomas> I have to say I'm not necessarly a big fan of this change. The
Thomas> _defconfig files used to be stored together with the kernel
Thomas> configuration, busybox configuration, uClibc configuration and target
Thomas> skeleton specific to a target (in target/device/<vendor>/<board>).
Thomas> Now, the _defconfig files are in a separate location, which makes it
Thomas> slightly less logical/easy for people to add new targets.
True - This change makes it slightly harder for developers, but easier
for users to find (and for us to do a test build of all defconfigs prior
to release).
The stuff in target/device/ tends to get stale over time, so a bit more
visibility is imho good.
I obviously like it, and I never had any comments when I proposed it
back in September:
http://lists.busybox.net/pipermail/buildroot/2009-September/029269.html
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-10-05 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-04 20:20 [Buildroot] [git commit master] buildroot; move defconfigs to configs/ and print in help Peter Korsgaard
2009-10-05 6:48 ` Thomas Petazzoni
2009-10-05 7:09 ` Peter Korsgaard [this message]
2009-11-11 14:03 ` Thomas Petazzoni
2009-11-11 18:36 ` Thiago A. Corrêa
2009-11-22 21:05 ` Peter Korsgaard
2009-11-25 22:02 ` Thomas Petazzoni
2009-11-25 22:16 ` Peter Korsgaard
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=873a5y5nbq.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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