From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] python-numpy: remove 2 dangling patches
Date: Wed, 29 Apr 2015 02:09:17 -0700 [thread overview]
Message-ID: <cover.1430298535.git.liezhi.yang@windriver.com> (raw)
The following changes since commit 4dd4b96b6d60246338bb30ede9f3ab1b2e757be9:
libxfont: Security Advisory - libxfont - CVE-2015-1804 (2015-04-28 07:56:01 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/python-numpy
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/python-numpy
Robert Yang (1):
python-numpy: remove 2 dangling patches
.../python/python-numpy/trycompile.diff | 36 --------------------
.../python/python-numpy/unbreak-assumptions.diff | 19 -----------
2 files changed, 55 deletions(-)
delete mode 100644 meta/recipes-devtools/python/python-numpy/trycompile.diff
delete mode 100644 meta/recipes-devtools/python/python-numpy/unbreak-assumptions.diff
--
1.7.9.5
next reply other threads:[~2015-04-29 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 9:09 Robert Yang [this message]
2015-04-29 9:09 ` [PATCH 1/1] python-numpy: remove 2 dangling patches Robert Yang
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.1430298535.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