All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Eggleton" <bluelightning@bluelightning.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH 2/2] bin/bitbake-getvar: Add a new command to query a variable value (with history)
Date: Tue, 20 Apr 2021 09:36:22 +1200	[thread overview]
Message-ID: <7360338.lvqk35OSZv@linc> (raw)
In-Reply-To: <20210416171126.1373752-2-richard.purdie@linuxfoundation.org>

On Saturday, 17 April 2021 05:11:26 NZST Richard Purdie wrote:
> We've talked about having this for long enough. Add a command which queries
> a single variable value with history. This saves "bitbake -e | grep" and
> avoids the various pitfalls that has.
> 
> It also provides a neat example of using tinfoil to make such a query.
> 
> Parameters to limit the output to just the value, to limit to a variable
> flag and to not expand the output are provided.
> 
> [YOCTO #10748]
> 
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

This is great, I have wanted to see this for quite a while! About the only 
feedback would be to add a short option for  --value, though I wonder if -v is 
the best option to choose or not given that it's typically short for "verbose" 
with most tools.

Cheers
Paul





  reply	other threads:[~2021-04-19 21:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 17:11 [PATCH 1/2] tinfoil/data_smart: Allow variable history emit() to function remotely Richard Purdie
2021-04-16 17:11 ` [PATCH 2/2] bin/bitbake-getvar: Add a new command to query a variable value (with history) Richard Purdie
2021-04-19 21:36   ` Paul Eggleton [this message]
2021-04-20 15:12     ` [bitbake-devel] " Ross Burton
2021-04-20 15:29       ` Christopher Larson
2021-04-23 18:03   ` Ola x Nilsson

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=7360338.lvqk35OSZv@linc \
    --to=bluelightning@bluelightning.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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.