From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] pkg-infra: add <pkg>_CONFIG_FIXUP to fix *-config files
Date: Fri, 18 Jan 2013 16:23:01 +0100 [thread overview]
Message-ID: <20130118162301.2a62ea79@skate> (raw)
In-Reply-To: <50F946E5.20903@petroprogram.com>
Dear Stefan Fr?berg,
On Fri, 18 Jan 2013 14:58:13 +0200, Stefan Fr?berg wrote:
> Sounds good but what about that <pkg>_CONFIG_FIXUP variable that was
> started from Gustavo suggestion (originally from divine-config: fixup
> thread) ?
>
> http://lists.busybox.net/pipermail/buildroot/2013-January/064656.html
>
> Was it now totally waste of time ? :-(
No, I think it's good. We should just give it some testing, add a bit
of documentation, and that's it. But in general, I'm in favor of this.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-18 15:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 19:52 [Buildroot] [PATCH v2] pkg-infra: add <pkg>_CONFIG_FIXUP to fix *-config files Stefan Fröberg
2013-01-10 19:52 ` Stefan Fröberg
2013-01-10 20:19 ` Thomas Petazzoni
2013-01-10 20:47 ` Yann E. MORIN
2013-01-10 21:15 ` Stefan Fröberg
2013-01-10 21:22 ` Yann E. MORIN
2013-01-10 21:01 ` Stefan Fröberg
2013-01-11 21:33 ` Arnout Vandecappelle
2013-01-12 1:38 ` Stefan Fröberg
2013-01-17 8:32 ` Arnout Vandecappelle
2013-01-18 12:58 ` Stefan Fröberg
2013-01-18 15:23 ` Thomas Petazzoni [this message]
2013-01-18 17:55 ` Stefan Fröberg
2013-01-18 15:51 ` Arnout Vandecappelle
2013-01-18 17:52 ` Stefan Fröberg
2013-01-20 11:36 ` Arnout Vandecappelle
2013-01-20 12:35 ` Samuel Martin
2013-01-20 14:37 ` Stefan Fröberg
2013-01-20 17:27 ` Arnout Vandecappelle
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=20130118162301.2a62ea79@skate \
--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