From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] epiphany: inherit perlnative
Date: Sat, 23 Jul 2016 22:16:39 -0700 [thread overview]
Message-ID: <cover.1469337362.git.liezhi.yang@windriver.com> (raw)
The following changes since commit 0a2df616a5c3316704742f1dcf37b450920e0280:
boost: fix CVE-2012-2677 (2016-07-21 07:45:01 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/epiphany
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/epiphany
Robert Yang (1):
epiphany: inherit perlnative
meta/recipes-gnome/epiphany/epiphany_3.20.3.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--
2.9.0
next reply other threads:[~2016-07-24 5:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 5:16 Robert Yang [this message]
2016-07-24 5:16 ` [PATCH 1/1] epiphany: inherit perlnative Robert Yang
2016-07-25 23:33 ` Burton, Ross
2016-07-27 1:17 ` Robert Yang
2016-07-27 9:34 ` Khem Raj
2016-07-27 9:37 ` Burton, Ross
2016-08-04 15:17 ` Burton, Ross
2016-08-04 17:54 ` Randle, William C
2016-08-05 2:47 ` Robert Yang
2016-08-05 8:20 ` Burton, Ross
2016-08-05 14:49 ` Khem Raj
2016-08-05 15:04 ` Burton, Ross
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.1469337362.git.liezhi.yang@windriver.com \
--to=liezhi.yang@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