My clone for meta-yocto is a bit old then, I checked this explicitly and it isn't a separate repo for me at all, hence why it's a single patch .. but wait. When I clone again from poky.git, it's still

I'm not particularly concerned about the kernel packages. I think we can ignore it. I'll update my script to not report these recipes. The main goal is to ensure that man pages and the like are being

Bruce, This need to be 2 pull requests, since the first 4 files are actually in meta-yotco, part of poky.git and the linux-yocto_git.bb is in OE-core Please split this into 2 requests, one for

I see "linux-*" in the list. What sort of documentation are we looking for? The linux-image* packages in Ubuntu, for example, include a changelog and a copyright. Thanks, -- Darren -- Darren

Hello, As a data point for where we stand in ensuring our packages are producing documentation, I have some scripts which build all recipes (using the output of bitbake -s, not world), and then check

Acked-by: Tom Zanussi <tom.zanussi@...> Pulled into meta-intel/master. Thanks, Paul!

The machine configuration of the non-core (non-qemu) machines has moved to meta-yocto. Moving the branch mappings, compatibility and SRCREVs of these machines to meta-yocto should also

The machine configuration of the non-core (non-qemu) machines has moved to meta-yocto. Moving the branch mappings, compatibility and SRCREVs of these machines to meta-yocto should also

From: Paul Eggleton <paul.eggleton@...> Signed-off-by: Paul Eggleton <paul.eggleton@...> --- .../recipes-core/tasks/task-core-tools.bbappend | 2 ++

From: Paul Eggleton <paul.eggleton@...> This adds back the emenlow-specific pieces recently removed from oe-core. Thanks, Paul Eggleton <paul.eggleton@...> --- Paul

Hi all, This is latest Yocto bug trend chart for WW18. The open bug number increased a lot from 182 to 185. Best Regards, Jiajun

Updating the linux-yocto/2.6.37 SRCREVs to pickup: perf tool: Fix gcc 4.6.0 issues 1/1 [ Author: Kyle McMartin Email: kyle@... Subject: perf tool: Fix gcc 4.6.0 issues

The BSP bootstrap and -dev use cases can be applied against unbranched or repos without meta data. To allow the proper and safe processing of those repositories, slight modifications to the tools are

To support quick uprev and testing, it is desireable to build repositories that do not have embedded meta data. In this scenario the meta data can be automatically created or provided externally. This

Richard/Saul, I've been running with these changes since before ELC, so they've had some good soak time. The first two changes lay the ground for for some 1.1 functionality and are used by recipes in

Hi Beth, M1, Yes there's definitely quite an overlap here and we should coordinate efforts. Will catch you later on IRC to organise some time. Cheers, Paul -- Paul Eggleton Intel Open Source

Most of the issues surrounding the license field is currently on my plate for M1.D License tracking Build a parser to do license tracking more gracefully and make sure all recipes are correct. (takes

The TSC was asked by the board to figure out the details of the election which we did in the first meeting as requested and provided our feedback back to the board. The board naturally has the

2011/5/3 Richard Purdie <richard.purdie@...> I don't think it is up to the TSC to decide on the re-election timeframe. As it stands the TSC got a 2 month mandate. See the quote above (from Philip's

The current situation was making the best of a bad set of circumstances, the plan is to hold elections and nothing has changed in that regard. This was discussed at the last TSC meeting and we