From: Joshua Lock <josh@linux.intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/2] Misc fixes
Date: Fri, 25 Feb 2011 10:52:12 +0000 [thread overview]
Message-ID: <cover.1298630947.git.josh@linux.intel.com> (raw)
From: Joshua Lock <josh@linux.intel.com>
A couple of minor patches the first to fix a warning when parsing lexically
incorrect recipes and the second removes a warning during the standard build.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: josh/misc
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=josh/misc
Thanks,
Joshua Lock <josh@linux.intel.com>
---
Joshua Lock (2):
bitbake/codeparser: fix raising of ShellSyntaxError
dropbear: add SRC_URI checksums
bitbake/lib/bb/codeparser.py | 4 ++--
meta/recipes-core/dropbear/dropbear_0.52.bb | 3 +++
2 files changed, 5 insertions(+), 2 deletions(-)
--
1.7.4
next reply other threads:[~2011-02-25 10:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 10:52 Joshua Lock [this message]
2011-02-25 10:52 ` [PATCH 1/2] bitbake/codeparser: fix raising of ShellSyntaxError Joshua Lock
2011-02-25 10:52 ` [PATCH 2/2] dropbear: add SRC_URI checksums Joshua Lock
2011-02-25 15:38 ` [PATCH 0/2] Misc fixes Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2011-07-21 9:29 [PATCH 0/2] Misc Fixes nitin.a.kamble
2011-07-21 21:08 nitin.a.kamble
2011-07-22 15:41 ` Saul Wold
2011-10-28 19:50 [PATCH 0/2] Misc fixes Jes.Sorensen
2012-01-19 13:59 Paul Eggleton
2012-04-13 4:43 [PATCH 0/2] Misc Fixes nitin.a.kamble
2012-04-26 22:53 [PATCH 0/2] Misc fixes nitin.a.kamble
2012-05-01 18:32 ` Saul Wold
2012-05-16 18:11 nitin.a.kamble
2013-07-27 14:35 [PATCH 0/2] misc fixes Tommi Rantala
2014-02-17 14:07 [PATCH 0/2] Misc fixes Paul Eggleton
2017-03-23 3:37 Khem Raj
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.1298630947.git.josh@linux.intel.com \
--to=josh@linux.intel.com \
--cc=poky@yoctoproject.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.