From: Kang Kai <Kai.Kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Fix can not stop systemd service var-volatile-lib
Date: Fri, 17 Jul 2015 16:54:12 +0800 [thread overview]
Message-ID: <55A8C2B4.1020804@windriver.com> (raw)
In-Reply-To: <cover.1436147616.git.kai.kang@windriver.com>
On 2015年07月06日 09:59, Kai Kang wrote:
> The following changes since commit 8ad9a434c9fd0300cf5c38c368b181b78421e95a:
>
> bitbake: tests/data: Add new data tests (2015-07-01 15:40:21 +0100)
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib kangkai/volatile-binds
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=kangkai/volatile-binds
>
> Kai Kang (1):
> volatile-binds: correct path of command umount
Ping?
>
> meta/recipes-core/volatile-binds/volatile-binds.bb | 1 +
> 1 file changed, 1 insertion(+)
>
--
Regards,
Neil | Kai Kang
prev parent reply other threads:[~2015-07-17 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 1:59 [PATCH 0/1] Fix can not stop systemd service var-volatile-lib Kai Kang
2015-07-06 1:59 ` [PATCH 1/1] volatile-binds: correct path of command umount Kai Kang
2015-07-17 11:47 ` Burton, Ross
2015-07-20 1:47 ` Kang Kai
2015-07-17 8:54 ` Kang Kai [this message]
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=55A8C2B4.1020804@windriver.com \
--to=kai.kang@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