<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">not integrate with yocto directly. but use it to 'manage' the set of trees that are required when using OE/Yocto. The gumstix guys are using it, see [1], and we are moving toward it at linaro too, to manage our builds [2]</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">[1] <a href="https://github.com/gumstix/Gumstix-YoctoProject-Repo" target="_blank">https://github.com/gumstix/Gumstix-YoctoProject-Repo</a></div><div class="gmail_extra">
[2] <a href="http://lists.linaro.org/pipermail/linaro-dev/2013-May/015998.html" target="_blank">http://lists.linaro.org/pipermail/linaro-dev/2013-May/015998.html</a></div>
<div class="gmail_extra"><br></div><div class="gmail_extra">then for organization that might need it, repo can be integrated with gerrit too, but repo 'standalone' can still be used to manage set of trees.</div>
<div class="gmail_extra"><br></div></div>
</blockquote></div><br>Thanks for the input. That's a good idea.
</div><div class="gmail_extra"><br></div><div class="gmail_extra">Rudi</div></div>