From: nitin.a.kamble@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] redo the glib-2.0 fix
Date: Thu, 21 Jul 2011 04:09:52 -0700 [thread overview]
Message-ID: <cover.1311246527.git.nitin.a.kamble@intel.com> (raw)
From: Nitin A Kamble <nitin.a.kamble@intel.com>
The following changes since commit db0eff4b964055b18ca5f91e55b7cf0d4a55c832:
python: fix security vulnerability (2011-07-21 02:23:27 -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 (1):
glib-2.0: fix a compilation issue due to dtrace
meta/recipes-core/glib-2.0/glib-2.0_2.27.5.bb | 2 +-
meta/recipes-core/glib-2.0/glib-2.0_2.28.8.bb | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
--
1.7.6
next reply other threads:[~2011-07-21 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 11:09 nitin.a.kamble [this message]
2011-07-21 11:09 ` [PATCH 1/1] glib-2.0: fix a compilation issue due to dtrace nitin.a.kamble
2011-07-22 7:22 ` Saul Wold
2011-07-22 15:40 ` [PATCH 0/1] redo the glib-2.0 fix Saul Wold
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.1311246527.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