From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: David Marchand <david.marchand@redhat.com>,
Arnon Warshavsky <arnon@qwilt.com>,
dev@dpdk.org, "Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] devtools: fix error propagation from check-forbidden-tokens.awk
Date: Thu, 17 Jan 2019 20:59:17 -0800 [thread overview]
Message-ID: <CACZ4nhuS=SdnhhC5SR+qv3VHJQn1WU70idDM0xxm2CD0rkp8=A@mail.gmail.com> (raw)
In-Reply-To: <1738126.GvICuaXjFY@xps>
On Thu, Jan 17, 2019 at 1:47 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> 17/01/2019 22:34, Ajit Khaparde:
> > On Thu, Jan 17, 2019 at 9:26 AM David Marchand <
> david.marchand@redhat.com>
> > wrote:
> >
> > > On Thu, Jan 17, 2019 at 4:33 PM Thomas Monjalon <thomas@monjalon.net>
> > > wrote:
> > >
> > >> 17/01/2019 13:20, David Marchand:
> > >> > On Fri, Dec 21, 2018 at 2:00 AM Thomas Monjalon <
> thomas@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.
>
> Interesting. Ajit, I think we never documented this process.
> Would you like to describe it briefly here:
> http://core.dpdk.org/contribute/#bugzilla
>
> Sure. I am working on it. But I think we need to also mention that
bugs will also be aged out if there is no activity on it for say "1" year?
Unless there is a valid reason to keep it open?
prev parent reply other threads:[~2019-01-18 4:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 14:03 [dpdk-dev] [PATCH v1] " Arnon Warshavsky
2018-12-18 14:12 ` David Marchand
2018-12-18 14:16 ` David Marchand
2018-12-18 14:27 ` David Marchand
2018-12-18 14:35 ` Thomas Monjalon
2018-12-18 14:44 ` Arnon Warshavsky
2018-12-18 14:48 ` Thomas Monjalon
2018-12-18 14:49 ` David Marchand
2018-12-18 14:53 ` Arnon Warshavsky
2018-12-18 14:55 ` David Marchand
2018-12-18 15:19 ` [dpdk-dev] [PATCH v2] " Arnon Warshavsky
2018-12-21 0:59 ` Thomas Monjalon
2019-01-17 12:20 ` David Marchand
2019-01-17 15:32 ` Thomas Monjalon
2019-01-17 17:25 ` David Marchand
2019-01-17 21:34 ` Ajit Khaparde
2019-01-17 21:47 ` Thomas Monjalon
2019-01-18 4:59 ` Ajit Khaparde [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACZ4nhuS=SdnhhC5SR+qv3VHJQn1WU70idDM0xxm2CD0rkp8=A@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=arnon@qwilt.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).