From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/1] Allow set +x for shell functions to be configured
Date: Mon, 27 Feb 2012 14:06:17 +0000 [thread overview]
Message-ID: <cover.1330351287.git.paul.eggleton@linux.intel.com> (raw)
A patch to allow the addition of "set +x" to be controlled via
configuration.
The patch (against Poky, but applies cleanly with -p2 against bitbake
master) is available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/bbverboselogs
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bbverboselogs
Paul Eggleton (1):
bitbake: implement BB_VERBOSE_LOGS
bitbake/lib/bb/build.py | 3 ++-
bitbake/lib/bb/cooker.py | 4 ++++
bitbake/lib/bb/msg.py | 5 ++++-
3 files changed, 10 insertions(+), 2 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-02-27 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 14:06 Paul Eggleton [this message]
2012-02-27 14:06 ` [PATCH 1/1] bitbake: implement BB_VERBOSE_LOGS Paul Eggleton
2012-02-27 14:08 ` Paul Eggleton
-- strict thread matches above, loose matches on Subject: below --
2012-02-27 14:11 [PATCH 0/1] Allow set +x for shell functions to be configured Paul Eggleton
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.1330351287.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox