From: Jack Mitchell <ml@communistcode.co.uk>
To: yocto@yoctoproject.org
Subject: Re: RFC: Hob 1.2 design
Date: Thu, 02 Feb 2012 10:12:47 +0000 [thread overview]
Message-ID: <4F2A619F.8020101@communistcode.co.uk> (raw)
In-Reply-To: <4F29764F.7000305@intel.com>
On 01/02/12 17:28, Scott Garman wrote:
> On 01/31/2012 05:39 PM, Wang, Shane wrote:
>> Hi, all,
>>
>> Belen has a new video for Hob2 workflow and design.
>>
>> https://wiki.yoctoproject.org/wiki/File:Hob1.2-screencast2.mov
>>
>> Please comment.
>
> I'm pretty amazed with this. The workflow seems clear and each screen
> provides just the right bits of information the user would be
> interested in seeing. Outstanding!
>
> Scott
>
I concur, it looks fantastic - well done!
It covers a lot more bases than I thought it would. Even if you still
like to do the build via CLI it gives a fantastic overview of the system
you're building as a whole, and even better, a dependency tree for why
certain packages are being included in the build.
next prev parent reply other threads:[~2012-02-02 10:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 1:39 RFC: Hob 1.2 design Wang, Shane
2012-02-01 3:15 ` Stewart, David C
2012-02-02 10:36 ` Barros Pena, Belen
2012-02-01 17:28 ` RFC: " Scott Garman
2012-02-02 10:12 ` Jack Mitchell [this message]
2012-02-06 21:32 ` Joshua Lock
2012-02-07 11:23 ` Barros Pena, Belen
2012-02-07 16:17 ` Joshua Lock
2012-02-08 10:23 ` Barros Pena, Belen
[not found] <3AB6CE7F274E534CAFD089D127A8A1FC0FCE9F5F@SHSMSX102.ccr.corp.intel.com>
[not found] ` <CB4F0427.6A93%belen.barros.pena@intel.com>
2012-02-02 12:48 ` Wang, Shane
2012-02-02 22:29 ` Joshua Lock
2012-02-03 0:25 ` Wang, Shane
2012-02-03 0:56 ` Xu, Dongxiao
2012-02-03 5:29 ` Wang, Shane
2012-02-03 15:01 ` Barros Pena, Belen
2012-02-06 11:53 ` Barros Pena, Belen
2012-02-03 0:35 ` Xu, Dongxiao
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=4F2A619F.8020101@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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.