From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] initscripts: Create the volatiles cache atomically.
Date: Fri, 02 Mar 2012 15:22:36 +0000 [thread overview]
Message-ID: <1330701756.309.9.camel@ted> (raw)
In-Reply-To: <1330478026-3871-1-git-send-email-james@digitalmatter.com.au>
On Wed, 2012-02-29 at 09:13 +0800, James Limbouris wrote:
> If a machine loses power while building the volatiles cache, it will
> continue to operate with an incomplete set of volatiles. Fix this by
> updating atomically.
>
> Signed-off-by: James Limbouris <james@digitalmatter.com.au>
> ---
> .../initscripts-1.0/populate-volatile.sh | 10 ++++++----
> meta/recipes-core/initscripts/initscripts_1.0.bb | 2 +-
> 2 files changed, 7 insertions(+), 5 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-03-02 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 1:13 [PATCH] initscripts: Create the volatiles cache atomically James Limbouris
2012-03-02 15:22 ` Richard Purdie [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=1330701756.309.9.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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