From: nitin.a.kamble@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] update upstream-status for at recipe patches
Date: Thu, 17 Nov 2011 15:13:38 -0800 [thread overview]
Message-ID: <cover.1321560182.git.nitin.a.kamble@intel.com> (raw)
From: Nitin A Kamble <nitin.a.kamble@intel.com>
The following changes since commit 3b3bf4134fdec13d31d98af3cdb31a7111a05e35:
gmp: also generate the libgmpcxx library (2011-11-17 10:25:22 -0800)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib nitin/work
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/work
Nitin A Kamble (1):
at: update the upstream-status of patches
.../at/at-3.1.12/configure-add-enable-pam.patch | 2 ++
.../at/files/file_replacement_with_gplv2.patch | 2 ++
.../at/files/nonstripbinaries.patch | 1 +
meta/recipes-extended/at/files/use-ldflags.patch | 2 ++
4 files changed, 7 insertions(+), 0 deletions(-)
--
1.7.6.4
next reply other threads:[~2011-11-17 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 23:13 nitin.a.kamble [this message]
2011-11-17 23:13 ` [PATCH 1/1] at: update the upstream-status of patches nitin.a.kamble
2011-11-23 18:54 ` [PATCH 0/1] update upstream-status for at recipe patches 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.1321560182.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