From: Scott Garman <scott.a.garman@intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: yocto@yoctoproject.org, "Purdie, Richard" <richard.purdie@intel.com>
Subject: Re: denzil bug status.
Date: Tue, 12 Jun 2012 11:33:39 -0700 [thread overview]
Message-ID: <4FD78B83.5040102@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1206121418560.15112@oneiric>
On 06/12/2012 11:20 AM, Robert P. J. Day wrote:
> On Tue, 12 Jun 2012, Scott Garman wrote:
>
>> Hello,
>>
>> As we are less than a week from our intended release candidate freeze
>> date (June 18) for the denzil point-release, I had a meeting with
>> Richard Purdie and Saul Wold to go over the final bug list and assess
>> the remaining work. Here is a summary of the results of that meeting.
>>
>> The bug numbers I'm referring to can be found on the Yocto Project
>> bugzilla site: https://bugzilla.yoctoproject.org
>
> ... snip ...
>
> was someone working on a fix for downloading tarballs that contain a
> "+" in the filename, to prevent them from being downloaded repeatedly?
> recall the recent issue i reported WRT the "gtk+" tarball, which was
> continually downloaded despite it being in my local mirror.
Looks like bug #2546 is tracking this:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2546
It has not been assigned a milestone, perhaps Richard can clarify if the
fix is intended/appropriate for 1.2.1.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-06-12 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 18:09 denzil bug status Scott Garman
2012-06-12 18:14 ` Scott Garman
2012-06-12 18:20 ` Robert P. J. Day
2012-06-12 18:33 ` Scott Garman [this message]
2012-06-12 18:41 ` Robert P. J. Day
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=4FD78B83.5040102@intel.com \
--to=scott.a.garman@intel.com \
--cc=richard.purdie@intel.com \
--cc=rpjday@crashcourse.ca \
--cc=yocto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.