From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "Dragomir, CalinX L" <calinx.l.dragomir@intel.com>,
"webhob@yoctoproject.org" <webhob@yoctoproject.org>
Subject: Re: [Webhob] Builds table information
Date: Thu, 6 Jun 2013 13:38:04 +0000 [thread overview]
Message-ID: <CDD64EB4.2B99C%belen.barros.pena@intel.com> (raw)
In-Reply-To: <20157495.MvgJknPJVN@helios>
Excellent: a question with an easy answer at last! ;)
Thanks, Paul
Belen
On 06/06/2013 14:33, "Paul Eggleton" <paul.eggleton@linux.intel.com> wrote:
>On Thursday 06 June 2013 13:18:31 Barros Pena, Belen wrote:
>> I've updated the builds table information
>> (https://bugzilla.yoctoproject.org/attachment.cgi?id=1244)
>>
>> By the way, what about the log question? It says:
>>
>> In Hob, we create a build log file. Should we do the same in Web Hob?
>
>We should be collecting the main cooker log in web hob as we do
>everywhere
>else, yes.
>
>Cheers,
>Paul
>
>--
>
>Paul Eggleton
>Intel Open Source Technology Centre
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2013-06-06 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CDD62EAD.2B890%belen.barros.pena@intel.com>
2013-06-06 13:18 ` [Webhob] Builds table information Barros Pena, Belen
2013-06-06 13:33 ` Paul Eggleton
2013-06-06 13:38 ` Barros Pena, Belen [this message]
2013-06-03 15:07 Barros Pena, Belen
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=CDD64EB4.2B99C%belen.barros.pena@intel.com \
--to=belen.barros.pena@intel.com \
--cc=calinx.l.dragomir@intel.com \
--cc=paul.eggleton@linux.intel.com \
--cc=webhob@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.