From: Saul Wold <sgw@linux.intel.com>
To: Scott Garman <scott.a.garman@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] runqemu fix for bug #5617
Date: Wed, 18 Dec 2013 09:42:45 -0800 [thread overview]
Message-ID: <52B1DE95.5040209@linux.intel.com> (raw)
In-Reply-To: <52B1DD24.5040606@intel.com>
On 12/18/2013 09:36 AM, Scott Garman wrote:
> Ping reminder on this patch.
>
I believe it was merged last week, did you update master?
Sau!
> Scott
>
> On 12/05/2013 01:57 PM, Scott Garman wrote:
>> Hi all,
>>
>> It's been a while since I've submitted a patch, let's see if I can get
>> this process right the first time. ;)
>>
>> This is a fix for Yocto bug #5617. Ross Burton wasn't a fan of the image
>> filename whitelist, and I have to agree - it's not very maintainable. So
>> when we have to guess the image filename, instead just pick the most
>> recently modified imgage filename that conforms to our typical naming
>> conventions, *image*machine.fstype
>>
>> Scott
>>
>> The following changes since commit
>> 300760193c6bcfd20f1d4908f912bebd53e86281:
>>
>> tcl: fix tclConfig.sh to point to the correct private headers
>> (2013-12-05 16:48:17 +0000)
>>
>> are available in the git repository at:
>>
>> git://git.openembedded.org/openembedded-core-contrib
>> sgarman/runqemu-imgfn-fix
>>
>> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgarman/runqemu-imgfn-fix
>>
>>
>> Scott Garman (1):
>> runqemu: remove core-image-* whitelist
>>
>> scripts/runqemu | 17 +++++------------
>> 1 file changed, 5 insertions(+), 12 deletions(-)
>>
>
>
next prev parent reply other threads:[~2013-12-18 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 21:57 [PATCH 0/1] runqemu fix for bug #5617 Scott Garman
2013-12-05 21:57 ` [PATCH 1/1] runqemu: remove core-image-* whitelist Scott Garman
2013-12-18 17:36 ` [PATCH 0/1] runqemu fix for bug #5617 Scott Garman
2013-12-18 17:42 ` Saul Wold [this message]
2013-12-18 18:34 ` Scott Garman
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=52B1DE95.5040209@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=scott.a.garman@intel.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