On 02/24/2017 10:27 AM, Patrick Ohly wrote: > On Fri, 2017-02-24 at 15:33 +0100, Gary Thomas wrote: >> On 2017-02-24 15:21, Patrick Ohly wrote: >>> On Wed, 2017-02-22 at 15:56 -0600, Jose Lamego wrote: >>>> >>>> On 02/22/2017 02:55 PM, Michael Halstead wrote: >>>>> I've seen several issues with hooks. I was working on them yesterday and >>>>> will continue today. >>>>> >>>>> These are currently managed by hand but we are moving them into >>>>> configuration management which should help keep them working consistently. >>>> >>>> Michael: one syntax error in patchwork code was pulled into production >>>> yesterday. This is the cause for missing patches. The error is fixed in >>>> the Yocto repo now, please perform a server code update ASAP. >>>> >>>> Martin: I will look at the UI issue you are describing and file a bug if >>>> needed. >>> >>> Would it perhaps make sense to reply to the original author with an >>> email confirming that his patch is now in Patchwork? It should include a >>> link to the patch series, too. >>> >>> This could have several advantages: >>> * submitters not aware of Patchwork or whether their target >>> currently uses it learn about it and then can follow the >>> progress of their patch >>> * everyone gets a confirmation that the submission made it through >>> the various mail servers and Patchwork itself >>> >>> It still relies on the original submitter to watch out for breakages in >>> the processes, but I guess that can't be avoided with an asynchronous, >>> mail-based process. >>> >> >> I would love to see this added to the process - +1 :-) > > Let me clarify that my original proposal was to reply only to the > original author. That was meant to keep noise down on the list. However, > perhaps it should also go to the list? > > Then others can help check that Patchwork works, as the original author > might not be aware that a response is missing. It also tells everyone > the relevant link in Patchwork. > There is a filed request to enable email notifications in patchwork: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7684
this notifications will let users (both submitter and CC'ed-users) know through an email about any patch status change (including "New"). Users will be able to opt-out of such notifications. However, this do not covers the case when submitter is not registered as a Patchwork user. So, there might be a one-time-only email notification to this kind of submitter, as Patrick suggests. If I don't get any objections for this, I'll file a request in bugzilla next week. -- Jose Lamego | OTC Embedded Platforms & Tools | GDC
signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core