From: Max Eliaser <max.eliaser@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Fix texinfo-dummy-native bug causing false-positive assertion errors
Date: Fri, 13 Jun 2014 15:07:40 -0700 [thread overview]
Message-ID: <cover.1402697205.git.max.eliaser@intel.com> (raw)
Hello list,
This is a simple one-line fix for Denys Dmytriyenko's bug.
Regards,
-Max Eliaser
The following changes since commit 5452824960e8e77005a25ac11fd069d927523d3e:
default-distrovars.inc: Remove unused variable 'LIMIT_BUILT_LOCALES' (2014-06-13 13:08:44 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib meliaser/fix-texinfo-dummy-capital-E
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=meliaser/fix-texinfo-dummy-capital-E
Max Eliaser (1):
texinfo-dummy-native: Fix dummy scripts failing when paths contain
capital Es
meta/recipes-extended/texinfo-dummy-native/texinfo-dummy/template.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.8.3.2
next reply other threads:[~2014-06-13 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 22:07 Max Eliaser [this message]
2014-06-13 22:07 ` [PATCH 1/1] texinfo-dummy-native: Fix dummy scripts failing when paths contain capital Es Max Eliaser
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.1402697205.git.max.eliaser@intel.com \
--to=max.eliaser@intel.com \
--cc=openembedded-core@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