From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] classes/buildhistory: actually use KiB in extensible SDK sizes files
Date: Tue, 5 Jan 2016 16:43:20 +1300 [thread overview]
Message-ID: <cover.1451965306.git.paul.eggleton@linux.intel.com> (raw)
Fix a minor mistake in my recent buildhistory extensible SDK changes.
The following changes since commit 1568f4fa1c8f8abd9b365ecd264841cd4f6b66b1:
bluez5: include the patch only for 5.36 (2015-12-28 13:02:03 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/buildhistory-sdk-kib
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/buildhistory-sdk-kib
Paul Eggleton (1):
classes/buildhistory: actually use KiB in extensible SDK sizes files
meta/classes/buildhistory.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.5.0
next reply other threads:[~2016-01-05 3:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 3:43 Paul Eggleton [this message]
2016-01-05 3:43 ` [PATCH 1/1] classes/buildhistory: actually use KiB in extensible SDK sizes files 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.1451965306.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