From: nitin.a.kamble@intel.com
To: Openembedded-core@lists.openembedded.org, yocto@yoctoproject.org
Subject: [PATCH 0/1] a fix for poky-tiny
Date: Fri, 8 Jun 2012 15:23:27 -0700 [thread overview]
Message-ID: <cover.1339194124.git.nitin.a.kamble@intel.com> (raw)
From: Nitin A Kamble <nitin.a.kamble@intel.com>
resending with corrected contrib branch.
The following changes since commit 0612cf3fcb3365e7721a2d5c331f8cd2647ae60b:
hob2: create a standalone deploy image tool (2012-06-08 12:13:43 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib master+work
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/master+work
Nitin A Kamble (1):
eglibc: remove runtime dependency of perl from eglibc-mtrace
meta/recipes-core/eglibc/eglibc-package.inc | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
--
1.7.3.4
next reply other threads:[~2012-06-08 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 22:23 nitin.a.kamble [this message]
2012-06-08 22:23 ` [PATCH 1/1] eglibc: remove runtime dependency of perl from eglibc-mtrace nitin.a.kamble
2012-06-08 23:02 ` Darren Hart
2012-06-11 22:07 ` [yocto] " Saul Wold
2012-06-11 22:08 ` Darren Hart
2012-06-11 22:25 ` Khem Raj
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.1339194124.git.nitin.a.kamble@intel.com \
--to=nitin.a.kamble@intel.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.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