From: Kang Kai <kai.kang@windriver.com>
To: <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] update distro tracking fields
Date: Thu, 28 Jul 2011 17:41:49 +0800 [thread overview]
Message-ID: <cover.1311845680.git.kai.kang@windriver.com> (raw)
From: Kang Kai <kai.kang@windriver.com>
Hi Saul,
I update the distro tracking fields of mailx slang libnewt and alsa-tools.
Because the mailx license file COPYING has lots of copyrights including personal,
company and MPL. I have no idea how to update the LICENSE and keep the STATUS "red".
Do you have any suggestion about that?
Thank you!
The following changes since commit 860a41bae6b863a289b06a9684d9cf6c58a307bd:
arch-ia32.inc: Fix up TUNE_ARCH variable conflicts (2011-07-26 22:39:59 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib kangkai/distro
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/distro
Kang Kai (2):
libnewt: update to 0.52.13
distro_tracking_fields: update packages info
.../conf/distro/include/distro_tracking_fields.inc | 28 +++++---
.../newt/files/include-without-python.patch | 73 --------------------
.../{libnewt_0.52.12.bb => libnewt_0.52.13.bb} | 7 +-
meta/recipes-extended/slang/slang_2.2.4.bb | 1 +
.../recipes-multimedia/alsa/alsa-tools_1.0.24.1.bb | 9 ++-
5 files changed, 28 insertions(+), 90 deletions(-)
delete mode 100644 meta/recipes-extended/newt/files/include-without-python.patch
rename meta/recipes-extended/newt/{libnewt_0.52.12.bb => libnewt_0.52.13.bb} (87%)
--
1.7.5.1.300.gc565c
next reply other threads:[~2011-07-28 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 9:41 Kang Kai [this message]
2011-07-28 9:41 ` [PATCH 1/2] libnewt: update to 0.52.13 Kang Kai
2011-07-28 15:40 ` Saul Wold
2011-07-28 9:41 ` [PATCH 2/2] distro_tracking_fields: update packages info Kang Kai
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.1311845680.git.kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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