From: nitin.a.kamble@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Misc Fixes
Date: Thu, 21 Jul 2011 14:08:43 -0700 [thread overview]
Message-ID: <cover.1311282465.git.nitin.a.kamble@intel.com> (raw)
From: Nitin A Kamble <nitin.a.kamble@intel.com>
The following changes since commit 8bd302b16dbd708fb9446fdc534ac64d873a34f5:
glib-2.0: fix a compilation issue due to dtrace (2011-07-21 14:01:33 -0700)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib nitin/misc
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/misc
Nitin A Kamble (2):
python: fix security vulnerability
fix Upstream-Status line for few patches
.../btrfs-tools/btrfs-tools/fix_use_of_gcc.patch | 2 +-
.../dosfstools/dosfstools-2.10-kernel-2.6.patch | 2 +-
.../elfutils/elfutils/fix_for_gcc-4.7.patch | 2 +-
meta/recipes-devtools/python/python.inc | 2 +-
.../python/python/security_issue_2254_fix.patch | 184 ++++++++++++++++++++
meta/recipes-devtools/python/python_2.6.6.bb | 3 +-
6 files changed, 190 insertions(+), 5 deletions(-)
create mode 100644 meta/recipes-devtools/python/python/security_issue_2254_fix.patch
--
1.7.6
next reply other threads:[~2011-07-22 3:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 21:08 nitin.a.kamble [this message]
2011-07-21 21:08 ` [PATCH 1/2] python: fix security vulnerability nitin.a.kamble
2011-07-21 21:08 ` [PATCH 2/2] fix Upstream-Status line for few patches nitin.a.kamble
2011-07-22 15:41 ` [PATCH 0/2] Misc Fixes Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2017-03-23 3:37 [PATCH 0/2] Misc fixes Khem Raj
2012-05-16 18:11 nitin.a.kamble
2012-04-26 22:53 nitin.a.kamble
2012-05-01 18:32 ` Saul Wold
2012-04-13 4:43 [PATCH 0/2] Misc Fixes nitin.a.kamble
2012-01-19 13:59 [PATCH 0/2] Misc fixes Paul Eggleton
2011-07-21 9:29 [PATCH 0/2] Misc Fixes nitin.a.kamble
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.1311282465.git.nitin.a.kamble@intel.com \
--to=nitin.a.kamble@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