From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yu Ke <ke.yu@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] check if lockfile is writable (bug 606 patch V2)
Date: Thu, 30 Dec 2010 09:29:11 +0000 [thread overview]
Message-ID: <1293701351.17519.9932.camel@rex> (raw)
In-Reply-To: <cover.1293616099.git.ke.yu@intel.com>
On Wed, 2010-12-29 at 17:54 +0800, Yu Ke wrote:
> I've sent a patch for bug 606 before, which add sanity check for $DL_DIR.
>
> After digging more, the root cause is hidden in bb.utils.lockfile(), so it
> is more general to add check there. hence comes out the V2 patch for bug606.
> please discard my V1 patch.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: kyu3/bug606-v2
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kyu3/bug606-v2
>
> Thanks,
> Yu Ke <ke.yu@intel.com>
Merged into master, thanks.
Richard
prev parent reply other threads:[~2010-12-30 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 9:54 [PATCH 0/1] check if lockfile is writable (bug 606 patch V2) Yu Ke
2010-12-29 9:54 ` [PATCH 1/1] bb.utils: check if lock file is writable, to fix bug 606 Yu Ke
2010-12-29 18:01 ` [PATCH 0/1] check if lockfile is writable (bug 606 patch V2) Saul Wold
2010-12-29 20:26 ` Richard Purdie
2010-12-30 2:19 ` Yu Ke
2010-12-30 9:29 ` 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=1293701351.17519.9932.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=ke.yu@intel.com \
--cc=poky@yoctoproject.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