From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] Support persistent /var/log
Date: Tue, 7 Apr 2015 11:10:22 +0800 [thread overview]
Message-ID: <55234A9E.5090006@windriver.com> (raw)
In-Reply-To: <cover.1427186518.git.Qi.Chen@windriver.com>
ping
Any comment on this one?
//Chen Qi
On 03/24/2015 04:42 PM, Chen Qi wrote:
> The following changes since commit d3fcfe346b3472170641d9194243c4bbe06b8585:
>
> systemd: fix firmware path to match linux-firmware (2015-03-23 11:27:13 +0000)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib ChenQi/persistent-var-log
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=ChenQi/persistent-var-log
>
> Chen Qi (4):
> bitbake.conf: add VOLATILE_LOG_DIR variable
> base-files: respect VOLATILE_LOG_DIR
> initscripts: support persistent /var/log
> package.bbclass: support persistent /var/log
>
> meta/classes/package.bbclass | 2 +-
> meta/conf/bitbake.conf | 4 ++
> meta/files/fs-perms-persistent-log.txt | 66 ++++++++++++++++++++++
> meta/recipes-core/base-files/base-files_3.0.14.bb | 4 +-
> .../initscripts/initscripts-1.0/volatiles | 1 -
> meta/recipes-core/initscripts/initscripts_1.0.bb | 3 +
> 6 files changed, 76 insertions(+), 4 deletions(-)
> create mode 100644 meta/files/fs-perms-persistent-log.txt
>
next prev parent reply other threads:[~2015-04-07 3:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 8:42 [PATCH 0/4] Support persistent /var/log Chen Qi
2015-03-24 8:42 ` [PATCH 1/4] bitbake.conf: add VOLATILE_LOG_DIR variable Chen Qi
2015-03-24 8:42 ` [PATCH 2/4] base-files: respect VOLATILE_LOG_DIR Chen Qi
2015-03-24 8:42 ` [PATCH 3/4] initscripts: support persistent /var/log Chen Qi
2015-03-24 8:42 ` [PATCH 4/4] package.bbclass: " Chen Qi
2015-04-07 3:10 ` ChenQi [this message]
2015-05-26 5:43 ` [PATCH 0/4] Support " ChenQi
2015-05-26 9:15 ` Paul Eggleton
2015-05-28 4:55 ` Khem Raj
2015-05-28 6:05 ` ChenQi
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=55234A9E.5090006@windriver.com \
--to=qi.chen@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