From: Kang Kai <Kai.Kang@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 0/2] Fix lsbinitscripts link problem
Date: Tue, 3 Jul 2012 09:42:31 +0800 [thread overview]
Message-ID: <4FF24E07.7010905@windriver.com> (raw)
In-Reply-To: <cover.1340873279.git.kai.kang@windriver.com>
On 2012年06月28日 17:35, Kang Kai wrote:
> Hi Saul,
>
> I update the initscripts to use update alternative way to install file functions.
> That make file functions provided by lsbinitscripts will be used instead of initscripts.
Could anyone give comments of these two patches?
Thanks.
Regards,
Kai
>
> Regards,
> Kai
>
> The following changes since commit 8ce8d25bcda0e2e0b62204d5ca5875dedcaacf7d:
>
> sanity.bbclass: Increase LAYER_CONF_VERSION to match bblayers change (2012-06-25 17:20:54 +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 (1):
> initscripts: use update-alternative to handle file functions
>
> Xiaofeng Yan (1):
> lsbinitscripts: Add a linking for functions.lsbinitscripts
>
> meta/recipes-core/initscripts/initscripts_1.0.bb | 10 ++++++++--
> meta/recipes-extended/lsb/lsbinitscripts_9.03.bb | 6 +++---
> 2 files changed, 11 insertions(+), 5 deletions(-)
>
next prev parent reply other threads:[~2012-07-03 1:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 9:35 [PATCH 0/2] Fix lsbinitscripts link problem Kang Kai
2012-06-28 9:35 ` [PATCH 1/2] initscripts: use update-alternative to handle file functions Kang Kai
2012-07-03 13:53 ` Richard Purdie
2012-06-28 9:35 ` [PATCH 2/2] lsbinitscripts: Add a linking for functions.lsbinitscripts Kang Kai
2012-07-07 0:43 ` Saul Wold
2012-07-09 1:33 ` Kang Kai
2012-07-03 1:42 ` Kang Kai [this message]
2012-07-03 4:04 ` [PATCH 0/2] Fix lsbinitscripts link problem Saul Wold
2012-07-03 5:49 ` 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=4FF24E07.7010905@windriver.com \
--to=kai.kang@windriver.com \
--cc=Zhenfeng.Zhao@windriver.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