ct.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Bob Feretich
>Sent: Thursday, May 08, 2014 4:25 PM
>To: yocto@yoctoproject.org
>Subject: Re: [yocto] Definition of Yocto tasks
>
>
>On 5/7/2014 5:58 AM, Paul Eggleton wrote:
>> On Tuesday 06 May 2014 15:23:45 Bob Fer
...@yoctoproject.org] On Behalf Of Bob Feretich
Sent: Monday, May 05, 2014 4:52 PM
To: yocto@yoctoproject.org
Subject: [yocto] Definition of Yocto tasks
Is there a document that provides a detailed definition of what each
these
tasks do?
Yocto, OE, and bitbake manuals tell us how to command a specific task to
be
t; boun...@yoctoproject.org] On Behalf Of Bob Feretich
> >>> Sent: Monday, May 05, 2014 4:52 PM
> >>> To: yocto@yoctoproject.org
> >>> Subject: [yocto] Definition of Yocto tasks
> >>>
> >>> Is there a document that provides a detaile
Subject: [yocto] Definition of Yocto tasks
Is there a document that provides a detailed definition of what each these
tasks do?
Yocto, OE, and bitbake manuals tell us how to command a specific task to be
run, but not what they do.
The task name provides a good hint sometimes, but often that is not
> >Subject: [yocto] Definition of Yocto tasks
> >
> >Is there a document that provides a detailed definition of what each these
> >tasks do?
> >Yocto, OE, and bitbake manuals tell us how to command a specific task to be
> >run, but not what they do.
> >
>
gt;Subject: [yocto] Definition of Yocto tasks
>
>Is there a document that provides a detailed definition of what each these
>tasks do?
>Yocto, OE, and bitbake manuals tell us how to command a specific task to be
>run, but not what they do.
>
>The task name provides a good hint sometime
Is there a document that provides a detailed definition of what each
these tasks do?
Yocto, OE, and bitbake manuals tell us how to command a specific task to
be run, but not what they do.
The task name provides a good hint sometimes, but often that is not
enough. Users shouldn't have to read t
