From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [jethro][PATCH 0/1] One backport for jethro
Date: Thu, 25 Feb 2016 09:29:54 +1300 [thread overview]
Message-ID: <cover.1456345722.git.paul.eggleton@linux.intel.com> (raw)
This is intended for after the imminent point release of course.
The following changes since commit 0c702756dd0009c4112028fbf2479a346867b32c:
build-appliance-image: Update to jethro head revision (2016-02-24 09:04:05 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/jethro-fixes3
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/jethro-fixes3
Craig McQueen (1):
os-release: put double-quotes around variable contents
meta/recipes-core/os-release/os-release.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.5.0
next reply other threads:[~2016-02-24 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 20:29 Paul Eggleton [this message]
2016-02-24 20:29 ` [jethro][PATCH 1/1] os-release: put double-quotes around variable contents 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.1456345722.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.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