From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: "Wang, Shane" <shane.wang@intel.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Cc: Giulia Piu <giulia@closertag.com>
Subject: Re: [PATCH 2/4] Hob: log for Hob and allow users to show logs after successful build
Date: Wed, 4 Apr 2012 15:13:20 +0000 [thread overview]
Message-ID: <CBA22274.C4EE%belen.barros.pena@intel.com> (raw)
In-Reply-To: <3AB6CE7F274E534CAFD089D127A8A1FC23B11E92@SHSMSX102.ccr.corp.intel.com>
Sorry Shane: on your previous email you said
>Only "build packages" will not write logs because there is no chance for
>Users to retrieve on the GUI.
From the above I understood build packages and build images would normally
create two separate logs, but you were changing that purely because there
is no option in Hob to retrieve the build packages log. So I offered to
provide an option in the Packages screen that would allow people to
retrieve such log, if Jessica, who reported the bug, deemed it appropriate.
If I understood incorrectly just ignore my comment.
Cheers
Belen
On 04/04/2012 10:56, "Wang, Shane" <shane.wang@intel.com> wrote:
>Do you mean the image details screen is too busy with "View logs"? It was
>designed by Giulia.
>
>Retrieving the packages build log in the packages screen is not good
>because the log is also for "build image"
>
>--
>Shane
>
>Barros Pena, Belen wrote on 2012-04-03:
>
>> Sorry: this was an omission on the design side. If deemed appropriate,
>>we
>> can incorporate an option to retrieve the packages build log in the
>> Packages screen. I'll leave it to Jessica, who reported 1991, to decide
>>if
>> this is something we should provide.
>>
>> Cheers
>>
>> Belen
>>
---------------------------------------------------------------------
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:[~2012-04-04 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 15:22 [PATCH 0/4] Continue Hob fixes Shane Wang
2012-04-02 15:22 ` [PATCH 1/4] Hob: add the "info" indication icon for "information" in the dialogs Shane Wang
2012-04-02 15:22 ` [PATCH 2/4] Hob: log for Hob and allow users to show logs after successful build Shane Wang
2012-04-03 9:25 ` Barros Pena, Belen
2012-04-04 9:56 ` Wang, Shane
2012-04-04 15:13 ` Barros Pena, Belen [this message]
2012-04-04 15:59 ` Zhang, Jessica
2012-04-04 16:43 ` Barros Pena, Belen
2012-04-05 14:49 ` Zhang, Jessica
2012-04-06 8:10 ` Barros Pena, Belen
2012-04-02 15:22 ` [PATCH 3/4] Hob: remove grab_default() for deploy button Shane Wang
2012-04-02 15:22 ` [PATCH 4/4] Hob: reset issue indication and build status before build starts on build details screen Shane Wang
2012-04-05 13:06 ` [PATCH 0/4] Continue Hob fixes Richard Purdie
2012-04-05 14:06 ` Wang, Shane
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=CBA22274.C4EE%belen.barros.pena@intel.com \
--to=belen.barros.pena@intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=giulia@closertag.com \
--cc=shane.wang@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 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.