From: Joshua Lock <joshua.g.lock@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/2] remove True option to getVar / getVarFlag calls
Date: Fri, 25 Nov 2016 16:30:21 +0000 [thread overview]
Message-ID: <cover.1480091225.git.joshua.g.lock@intel.com> (raw)
My patch 1/2 is held for moderation so here's a cover letter pointing to
a branch with the two patches which remove the True option to getVar()
and getVarFlag () calls now that expanding is the default.
The following changes since commit d140f0ee6f301264e226914766d9f63558acfd6c:
COW.py: fix sample codes (2016-11-23 10:59:49 +0000)
are available in the git repository at:
https://github.com/incandescant/bitbake.git joshuagl/getvar
https://github.com/incandescant/bitbake/tree/joshuagl/getvar
Joshua Lock (2):
bitbake: remove True option to getVar calls
bitbake: remove True option to getVarFlag calls
bin/bitbake-layers | 2 +-
bin/bitbake-worker | 6 +-
.../bitbake-user-manual-fetching.xml | 4 +-
.../bitbake-user-manual-metadata.xml | 8 +--
lib/bb/build.py | 46 +++++++--------
lib/bb/cache.py | 10 ++--
lib/bb/cooker.py | 42 ++++++-------
lib/bb/cookerdata.py | 12 ++--
lib/bb/data.py | 26 ++++-----
lib/bb/data_smart.py | 16 ++---
lib/bb/fetch2/__init__.py | 68 +++++++++++-----------
lib/bb/fetch2/clearcase.py | 10 ++--
lib/bb/fetch2/cvs.py | 14 ++---
lib/bb/fetch2/git.py | 12 ++--
lib/bb/fetch2/hg.py | 10 ++--
lib/bb/fetch2/local.py | 12 ++--
lib/bb/fetch2/npm.py | 20 +++----
lib/bb/fetch2/osc.py | 10 ++--
lib/bb/fetch2/perforce.py | 8 +--
lib/bb/fetch2/repo.py | 4 +-
lib/bb/fetch2/sftp.py | 2 +-
lib/bb/fetch2/ssh.py | 4 +-
lib/bb/fetch2/svn.py | 2 +-
lib/bb/fetch2/wget.py | 12 ++--
lib/bb/monitordisk.py | 4 +-
lib/bb/parse/__init__.py | 2 +-
lib/bb/parse/ast.py | 14 ++---
lib/bb/parse/parse_py/BBHandler.py | 2 +-
lib/bb/parse/parse_py/ConfHandler.py | 6 +-
lib/bb/persist_data.py | 4 +-
lib/bb/providers.py | 12 ++--
lib/bb/runqueue.py | 32 +++++-----
lib/bb/siggen.py | 14 ++---
lib/bb/tests/codeparser.py | 12 ++--
lib/bb/tests/data.py | 58 +++++++++---------
lib/bb/tests/parse.py | 28 ++++-----
lib/bb/utils.py | 16 ++---
lib/bblayers/action.py | 2 +-
lib/bblayers/common.py | 2 +-
lib/bblayers/layerindex.py | 8 +--
lib/bblayers/query.py | 10 ++--
lib/prserv/serv.py | 4 +-
42 files changed, 295 insertions(+), 295 deletions(-)
--
2.7.4
reply other threads:[~2016-11-25 16:30 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=cover.1480091225.git.joshua.g.lock@intel.com \
--to=joshua.g.lock@intel.com \
--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.