[dpdk-dev] [PATCH v2] devtools: fix error propagation from check-forbidden-tokens.awk

Ajit Khaparde ajit.khaparde at broadcom.com
Thu Jan 17 22:34:47 CET 2019


On Thu, Jan 17, 2019 at 9:26 AM David Marchand <david.marchand at redhat.com>
wrote:

> On Thu, Jan 17, 2019 at 4:33 PM Thomas Monjalon <thomas at monjalon.net>
> wrote:
>
>> 17/01/2019 13:20, David Marchand:
>> > On Fri, Dec 21, 2018 at 2:00 AM Thomas Monjalon <thomas at monjalon.net>
>> wrote:
>> >
>> > > 18/12/2018 16:19, Arnon Warshavsky:
>> > > > Bugzilla ID: 165
>> > >
>> >
>> > Thomas,
>> >
>> > I just noticed that the bz is still opened.
>> > Who is supposed to close bug reports ?
>>
>> I think we never formally described this workflow.
>>
>> I suggest to expect the bug reporter to close the bug.
>>
>
> Well, the reporter is most likely able to reproduce an issue and confirm
> it is fixed.
> So +1 for me.
>
Unless I miss an update, I generally try to assign the BZ back to the
reporter to get an agreement,
or confirmation as needed and get the BZ closed.
So +1 for me as well.

Thanks
Ajit

>
>
> --
> David Marchand
>


More information about the dev mailing list