From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/1] Makefile: add variable print capabilities
Date: Sun, 26 May 2013 21:44:45 +0200 [thread overview]
Message-ID: <20130526214445.03abd9d3@skate> (raw)
In-Reply-To: <20130526194014.GC3380@free.fr>
Dear Yann E. MORIN,
On Sun, 26 May 2013 21:40:14 +0200, Yann E. MORIN wrote:
> > Hum, is this really useful? What are the use cases? What do other
> > thinks about this?
>
> I like the overall idea, but only for printing all variables.
> It's then possible to grep the result to find the one variable one is
> interested in.
>
> I've taken that patch in my tree (dropped the per-variable print, and
> adapted the printvars a bit), and will send a pull request to Peter
> later tonight.
I would suggest to not send patches touching the core infrastructure as
part of a pull request that also has many usually uncontroversial
package changes/updates.
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-05-26 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 19:01 [Buildroot] [PATCH 0/1] Makefile: add variable print capabilities Emeric Vigier
2012-07-19 19:01 ` [Buildroot] [PATCH] " Emeric Vigier
2012-07-19 20:08 ` [Buildroot] [PATCH 0/1] " Thomas Petazzoni
2012-07-19 22:25 ` Émeric Vigier
2013-05-26 19:40 ` Yann E. MORIN
2013-05-26 19:44 ` Thomas Petazzoni [this message]
2013-05-26 19:48 ` Yann E. MORIN
2013-05-26 20:03 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2012-07-19 18:29 Emeric Vigier
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=20130526214445.03abd9d3@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 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.