[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] automation: Creating a patchwork instance to improve pre-commit build testing



FWIW,

On Tue, 2018-07-24 at 16:26 +0100, George Dunlap wrote:
> On 07/24/2018 12:23 PM, Lars Kurth wrote:
> > 
> > It seems to me there are a number of options we have and thus some
> > decisions
> > that need to be made.

> > 2: Do we have an opt-in or op-out (e.g. through a tag, a specific
> > CC, etc.) for patches
> 
> Opt-out.
>
+1

> > 5: Do we report back on success or only on failure?
> > See question by Julien
> 
> I'd start with having the bot respond to 00/NN exactly once, both on
> success and failure.
> 
+1

> > 4: Who else, besides the author should get a mail
> > The patch submitters should definitely get a mail, the question is
> > whether people on the CC list should also get one
> 
> I think the bot should reply-to-all.  Maybe we can add an opt-out to
> our
> website, so that the bot won't reply to you if you don't want it to.
> 
+1

:-)

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.