<div class="gmail_quote">On Wed, Feb 1, 2012 at 15:07, McClintock Matthew-B29882 <span dir="ltr"><<a href="mailto:B29882@freescale.com">B29882@freescale.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Wed, Feb 1, 2012 at 10:04 AM, Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>> wrote:<br>
> Hi<br>
><br>
> patchwork instance that we have currently handles patches for<br>
> oe-devel, oe-core and bitbake<br>
> layers which use oe-devel maintain and use the patch queues ok so it<br>
> makes sense to have it<br>
> there. But patch flow for oe-core and bitbake is handled differently<br>
> via pull requests. Would it<br>
> make sense to turn it off for these two projects. Is someone using<br>
> patchwork and/or finds<br>
> it useful to have the patchwork catch those patches please let me know<br>
<br>
</div>Patchworks is useful for pulling patches into a git repo and having<br>
discussion on a patch documented. I don't think it should just be<br>
turned off, it can be left there for all the see and use.</blockquote><div><br></div><div>The major issue with it is the burden work of keeping it clean regarding of the merged patches. Otherwise it ends being useless due the amount of not archived patches.</div>
<div> </div></div>-- <br>Otavio Salvador O.S. Systems<br>E-mail: <a href="mailto:otavio@ossystems.com.br" target="_blank">otavio@ossystems.com.br</a> <a href="http://www.ossystems.com.br" target="_blank">http://www.ossystems.com.br</a><br>
Mobile: +55 53 9981-7854 <a href="http://projetos.ossystems.com.br" target="_blank">http://projetos.ossystems.com.br</a><br><br>