From: Yi Zhao <yi.zhao@windriver.com>
To: "Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: Reducing nightly/release build artifacts.
Date: Tue, 1 Apr 2014 13:33:06 +0800 [thread overview]
Message-ID: <533A4F92.90903@windriver.com> (raw)
In-Reply-To: <CAPhnLPDGY8ydV5jyRH=bLk=sAoj=c4ZP=b8Rx=1n6tfdG1Zbkg@mail.gmail.com>
Hi Beth,
于 2014年04月01日 02:38, Flanagan, Elizabeth 写道:
> Otavio
>
> So, if I were to not publish the fsl builds, would that be an issue?
Please do not remove p1022ds images from fsl-ppc build. I'm using it.
Thanks,
Yi
>
> -b
>
> On Fri, Mar 28, 2014 at 6:02 AM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> Hello Beth,
>>
>> On Wed, Mar 26, 2014 at 6:22 PM, Otavio Salvador
>> <otavio@ossystems.com.br> wrote:
>>> On Wed, Mar 26, 2014 at 6:14 PM, Flanagan, Elizabeth
>>> <elizabeth.flanagan@intel.com> wrote:
>>>> I'd like to start looking at reducing the number of artifacts we're
>>>> releasing both for our nightly builds (which is at 250,000 artifacts
>>>> and .25 TB!) and releases.
>> I don't use any meta-fsl-arm artifacts as I usually build the images
>> for testing, as does Daiane, however the autobuilder is critical for
>> me as your build does spot and exercise other things which mine does
>> not (plus the MUT) so I highly depend on it.
>>
>> --
>> Otavio Salvador O.S. Systems
>> http://www.ossystems.com.br http://code.ossystems.com.br
>> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
>
>
prev parent reply other threads:[~2014-04-01 5:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 21:14 Reducing nightly/release build artifacts Flanagan, Elizabeth
2014-03-26 21:22 ` Otavio Salvador
2014-03-26 21:30 ` Flanagan, Elizabeth
2014-03-28 2:23 ` Yi Zhao
2014-03-28 8:20 ` Georgescu, Alexandru C
2014-03-28 13:02 ` Otavio Salvador
2014-03-31 18:38 ` Flanagan, Elizabeth
2014-03-31 18:39 ` Otavio Salvador
2014-04-01 5:33 ` Yi Zhao [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=533A4F92.90903@windriver.com \
--to=yi.zhao@windriver.com \
--cc=elizabeth.flanagan@intel.com \
--cc=otavio@ossystems.com.br \
--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.