From: Rongqing Li <rongqing.li@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] glibc: package nscd related files
Date: Tue, 18 Aug 2015 16:14:37 +0800 [thread overview]
Message-ID: <55D2E96D.2040603@windriver.com> (raw)
In-Reply-To: <55CD444D.50203@windriver.com>
On 2015年08月14日 09:28, Rongqing Li wrote:
> On 2015年08月14日 00:31, Khem Raj wrote:
>>
>>> On Aug 13, 2015, at 1:09 AM, rongqing.li@windriver.com wrote:
>>>
>>> From: Roy Li <rongqing.li@windriver.com>
>>>
>>> install nscd related configuration file, startup files, and package
>>> them,
>>> make nscd easy to startup
>>>
>>
>> please test this change on top of glibc 2.22 recipe upgrade patches
>> which are in flight right now
>>
>
> if glibc 2.22 is merged, I will test it
>
> thanks
>
> -Roy
This patch works with glibc 2.22, please consider to accept it;
thanks
--
Best Reagrds,
Roy | RongQing Li
next prev parent reply other threads:[~2015-08-18 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 8:09 [PATCH] glibc: package nscd related files rongqing.li
2015-08-13 16:31 ` Khem Raj
2015-08-14 1:28 ` Rongqing Li
2015-08-18 8:14 ` Rongqing Li [this message]
2015-08-18 11:48 ` Burton, Ross
2015-08-19 1:22 ` Rongqing Li
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=55D2E96D.2040603@windriver.com \
--to=rongqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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