Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Christopher Larson <clarson@kergoth.com>
Cc: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: Re: should "bitbake -e" refer to per-recipe, not per-package?
Date: Tue, 22 Jul 2014 12:36:52 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407221236210.8695@localhost> (raw)
In-Reply-To: <CABcZAN=nRqo7sYm9=MkAT0r0uAnR_oVBMEnMYGJz_=h-mZ6p2Q@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 849 bytes --]

On Tue, 22 Jul 2014, Christopher Larson wrote:

> On Tue, Jul 22, 2014 at 3:19 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>         i notice that, in "bitbake -h", the explanation of "bibake -e" is
>       that it potentially allows the display of "per-package" environment
>       info. should that not more accurately say "per-recipe"?
>
>
> Yep.

  ok, i'll submit patch for that tonight.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

      reply	other threads:[~2014-07-22 16:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 10:19 should "bitbake -e" refer to per-recipe, not per-package? Robert P. J. Day
2014-07-22 15:13 ` Christopher Larson
2014-07-22 16:36   ` Robert P. J. Day [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=alpine.LFD.2.11.1407221236210.8695@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=clarson@kergoth.com \
    /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