<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 2, 2015 at 10:43 AM, Burton, Ross <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>></span> wrote:<br><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"><span class=""><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 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></span>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><span class="HOEnZb"><font color="#888888"><div class="gmail_extra"><br></div></font></span></div></blockquote><div>I agree with Ross that if we can get the functionality we truly need into Patchwork--and JaMa can live with the result or help guide the functionality--that we have a better path into the future.</div><div><br></div><div>Also, for what it's worth I vote for spaces only. We can provide editor templates/settings to make it easy on the end users. There are languages that require tabs, there are languages that require spaces. Deal with the required tabs when the necessary evil arises.</div><div><br></div><div>--Tim </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br></blockquote></div><br></div></div>