Agreed. I don't know what gitolite is capable of. I would really like to be able to create and destroy my own repositories in a central location with other Yocto developers. However, this doesn't

Agreed with the points above. git really is just wrangling a bunch of objects into commit chains and a branch points to a starting point. So I completely agree that all chains don't have to lead

Hi, Can someone please tell me what needs to be done to build qemu-system-mipsel or provide a patch for it? openembedded seems to be able to build something like this, so maybe it would not be too

I think there are three elements to this: a) People do like the logical separation that a repo gives them and find it easiest to think in those terms. b) Most people are used to single relatively

From: Liping Ke <liping.ke@...> Subject: [PATCH 1/1] Resend:[Image-Creator]Make bitbake server type configurable (xmlrpc, none) Add -t options in bitbake for configuring server

From: Liping Ke <liping.ke@...> Add -t options in bitbake for configuring server type. Signed-off-by: Liping Ke <liping.ke@...> Pull URL: git://git.pokylinux.org/poky-contrib.git

most if not all meego repo is on gitorious, why can't Yocto leverage it, at least for now while everything is changing fast? Xianghua <bruce.ashfield@...> wrote:

FYI - If you'd like to view the Yocto schedule at-a-glance, see the file linked to at the top of the Yocto schedule Wiki: https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule. -

This is what I was wondering as well. I had my meta-kernel-dev as a branch on poky-extras and ran into exactly this problem. Either have two clones, or get it into master. Master was the choice,

I'm curious how many people reading this feel this is "basic git". Anyone willing to admit this was the first time they have seen a targeted branch fetch used to avoid a larger download? If everyone

Just to add to this discussion, with gitolite, it should be easy to setup a yocto-contrib repo where each user "owns" the branches under <keyname>/*. This means as ssh keys are added, they'd

Different use case from what I'm seeing as the general concern, however, I would say that if someone has code that doesn't belong in oe-core but it's standalone and useful to the project, then you

I don't agree. I have a few sparse layers and some other code that I am not sharing because they need repositories *somewhere*. Having said that some of these recipes may be useful to others

A few notes, since I talked with Darren about this earlier. As one of the people in charge of maintaining the git repo, I would like to avoid having, as Darren suggested, a whole bunch of -contrib

Hi all, This is the weekly test report for Yocto 20110423 build. All meta-intel BSP build are failed on autobuilder. A new boot up failure bug is found on both routerstationpro and

I think that is a fantastic idea, it gets my vote. gitorious++ -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

This is one simple patch to fix seg fault of evolution-data-server, when new contact is added for new created DB. The root cause is simple: do_create (bf, XIMIAN_VCARD,....) would

Op 27 apr 2011, om 05:00 heeft Darren Hart het volgende geschreven: Have you though about setting up a gitorious instance on git.yocto? Regards, Koen

Well, sort of. The personal trees would be writable only by their owner. Otherwise you would have to manage all the user authentication. I forgot about the new meta-intel contributors. I would

Yeah, that's what you and I do already. But we now have people coming online who will be be continually pushing changes to their bsps in meta-intel and we don't necessarily want to give them write