From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Disable dtrace and system tap for glib-2.0-native
Date: Wed, 17 Aug 2011 09:24:53 -0700 [thread overview]
Message-ID: <cover.1313598136.git.josh@linux.intel.com> (raw)
Per discussion on the Yocto mailing list:
https://lists.yoctoproject.org/pipermail/yocto/2011-August/004571.html
Regards,
Joshua
The following changes since commit 2e83e6755441cb14bd907d306974338c15173189:
kernel: restore crtsavres.o to enable building external modules on powerpc (2011-08-17 15:46:16 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib josh/work
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=josh/work
Joshua Lock (1):
glib-2.0: explicitly disable dtrace and systemtap for native varaint
meta/recipes-core/glib-2.0/glib.inc | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--
1.7.6
next reply other threads:[~2011-08-17 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 16:24 Joshua Lock [this message]
2011-08-17 16:24 ` [PATCH 1/1] glib-2.0: explicitly disable dtrace and systemtap for native varaint Joshua Lock
2011-08-23 1:02 ` [PATCH 0/1] Disable dtrace and system tap for glib-2.0-native 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.1313598136.git.josh@linux.intel.com \
--to=josh@linux.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