From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-python][PATCH 0/2] Extend django recipes to nativesdk
Date: Tue, 17 Feb 2015 09:55:22 +0000 [thread overview]
Message-ID: <cover.1424166886.git.paul.eggleton@linux.intel.com> (raw)
I forgot to do this in the original versions.
The following changes since commit 9b15b3269062dbc48445be9bdc8beccee0cd7054:
opensc: add new recipe (2015-02-12 19:37:20 +0100)
are available in the git repository at:
git://git.openembedded.org/meta-openembedded-contrib paule/python-django-nativesdk
http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=paule/python-django-nativesdk
Paul Eggleton (2):
python-django: extend to nativesdk
python-django-south: extend to nativesdk
meta-python/recipes-devtools/python/python-django-south_1.0.2.bb | 1 +
meta-python/recipes-devtools/python/python-django_1.6.10.bb | 1 +
2 files changed, 2 insertions(+)
--
1.9.3
next reply other threads:[~2015-02-17 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 9:55 Paul Eggleton [this message]
2015-02-17 9:55 ` [meta-python][PATCH 1/2] python-django: extend to nativesdk Paul Eggleton
2015-02-17 9:55 ` [meta-python][PATCH 2/2] python-django-south: " 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.1424166886.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.