On Thu, Feb 22, 2018 at 3:35 PM, David Miller <da...@davemloft.net> wrote:
> From: Dmitry Vyukov <dvyu...@google.com>
> Date: Thu, 22 Feb 2018 10:58:07 +0100
>> Do I understand it correctly that if syzbot replies to the CC list
>> that was in the testing request, it will resolve the problem? So if
>> netdev wasn't in CC, it will not be added to CC.
>> I will go and fix it now.
> I don't want syzbot to send the patch to netdev, even if it
> was in the CC: list.
> And again this goes for netfilter-devel and linux-wireless as
> well.
> There is no reason whatsoever for syzbot to ever post an already
> posted patch back to the list again, even if it was on the CC:
> list.
> In fact netdev will be on that CC: list most of the time.

Hi David,

We've found a simple and reasonable solution with Daniel.
If we prefix subjects of these replies with "Re: " then Patchwork will
never treat them as new patches (always as a comment).
This is now implemented and deployed for syzbot:
So we now have 2 lines of defense for the problem never happening again.

Thanks for bringing it up.

Reply via email to