The discussion was triggered in the Yocto Project Technical Team Meeting from
June 19th.
-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com]
Sent: Wednesday, June 20, 2012 2:23 AM
To: Serban, Laurentiu
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] VERIFIED vs CLOSED i
On 20 June 2012 00:22, Darren Hart wrote:
> What is the reasoning driving this change? What does CLOSED indicate
> that VERIFIED does not already convey?
Agreed -- hiding CLOSED would be my proposal as it doesn't add any
meaning, just complicates the lifecycle.
Ross
_
On Wed, Jun 20, 2012 at 2:18 AM, Burton, Ross wrote:
>
> Agreed -- hiding CLOSED would be my proposal as it doesn't add any
> meaning, just complicates the lifecycle.
I think yes hiding closed it ok since it does not change much in fix.
I wouldnt say it complicates but it completes the life cycle
Hello,
Considering the following code snippet variants of a recipe which does
the same job, I would like to clarify certain doubts regarding this.
python __anonymous () {
pn_split = d.getVar('PN', True).split('-')
...
}
python __anonymous () {
import bb
pn_split =
On 06/20/2012 08:27 AM, Khem Raj wrote:
On Wed, Jun 20, 2012 at 2:18 AM, Burton, Ross wrote:
Agreed -- hiding CLOSED would be my proposal as it doesn't add any
meaning, just complicates the lifecycle.
I think yes hiding closed it ok since it does not change much in fix.
I wouldnt say it comp
On Wed, Jun 20, 2012 at 8:48 AM, Saul Wold wrote:
> The bug verification is the responsibility of the submitter, not the
> assignee/owner.
ok, in some workflows verified is owned by testting/qa person, I was
assuming that
when testing validates the bug fix it sets the state to verified and
owner
In Hob, we use a drop-down list to select your image. But with 19 base
images now available, we have already outgrown the capacity of this UI
widget (the guidelines recommend using them when you have between 3 and 10
items). I filed bug 2345 (nice number) to look at alternative ways of
presenting a
Does anybody know why are we calling it 'self-hosted-image' in Hob and
'build-appliance' in the Yocto Project website? Wouldn't it be easier if
we used the same name everywhere? Which one should be used?
Thanks!
Belen
-
Intel Co
On 06/20/2012 09:23 AM, Barros Pena, Belen wrote:
Does anybody know why are we calling it 'self-hosted-image' in Hob and
'build-appliance' in the Yocto Project website? Wouldn't it be easier if
we used the same name everywhere? Which one should be used?
They are slightly different. The self-hos
On Wed, Jun 20, 2012 at 9:17 AM, Barros Pena, Belen
wrote:
> In Hob, we use a drop-down list to select your image. But with 19 base
> images now available, we have already outgrown the capacity of this UI
> widget (the guidelines recommend using them when you have between 3 and 10
> items). I file
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02000
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Barros Pena, Belen
>Sent: Wednesday, June 20, 2012 9:24 AM
>
>Does anybody know why are we calling it 'self-hosted-image' in Hob and
>'build-appliance' in the Yocto Project website? Wouldn't it be easier i
Yep it's the same but what is the solution?? anything just wait for somebody
solved it??
I need another solution plase :S Need to compile the meta-intel layer
regards
Javier
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.o
About Jim’s video requirement. and many users to many bitbake servers mapping.
maybe there are some problems maybe to solve.
Some my questions:
1. running builds remaining time. difficult to estimate.
when a user check all the builds status, whether they are done or not.
the remaining time,
14 matches
Mail list logo