From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: a couple trivial questions about variable flags
Date: Wed, 9 Jul 2014 07:49:42 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407090745340.5513@localhost> (raw)
(again, potentially trivial and silly questions coming, but i'm long
past the point of personal shame. :-)
first, there is no need to pre-define variable flags, correct? i'm
reading BB user manual, section 3.1.10, regarding "Variable Flag
Syntax", and there's nothing to warn the reader whether or not they
need to define a variable flag before subsequently using it, so i was
thinking of adding that note.
also, same section, i think i'll submit a patch showing at least a
couple common uses for variable flags, the ones that leap to mind are:
[doc]
[md5sum]
[sha256sum]
since those can be seen absolutely everywhere.
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-09 11:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1407090745340.5513@localhost \
--to=rpjday@crashcourse.ca \
--cc=bitbake-devel@lists.openembedded.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.