<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 2 December 2015 at 18:04, Martin Jansa <span dir="ltr"><<a href="mailto:martin.jansa@gmail.com" target="_blank">martin.jansa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":6y4" class="a3s" style="overflow:hidden">I'm depending on bundles heavily, to "mark" the patches for layers with<br>
dedicated maintainer and also for extra "status" like merged in<br>
"master-next" branch for jenkins build, because standard status values<br>
aren't fine-grained enough.</div></blockquote></div><br>Sounds like instead of bundles the new patchworks needs the ability for a single list to represent multiple projects (so there'd be a meta-oe, meta-python, etc), and more status values.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>