From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] pseudo 1.6.1
Date: Fri, 18 Jul 2014 13:49:24 -0500 [thread overview]
Message-ID: <cover.1405709256.git.peter.seebach@windriver.com> (raw)
* Remove the uninformative "already offline" message.
* Stop trying to request x86-specific versions of memcpy on
non-x86.
Tarball's been submitted to pidge but may take a while to show up.
The following changes since commit a449598a839e677e2a094aa4bd9a68003de6e42e:
bdwgc: Add PACKAGECONFIG for libatomic-ops (2014-07-17 15:04:07 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/pseudo-161
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/pseudo-161
Peter Seebach (1):
pseudo: uprev to 1.6.1
.../pseudo/{pseudo_1.6.0.bb => pseudo_1.6.1.bb} | 4 ++--
meta/recipes-devtools/pseudo/pseudo_git.bb | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-devtools/pseudo/{pseudo_1.6.0.bb => pseudo_1.6.1.bb} (52%)
next reply other threads:[~2014-07-18 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 18:49 Peter Seebach [this message]
2014-07-18 18:49 ` [PATCH 1/1] pseudo: uprev to 1.6.1 Peter Seebach
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.1405709256.git.peter.seebach@windriver.com \
--to=peter.seebach@windriver.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