All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Arnon Warshavsky <arnon@qwilt.com>,
	dev@dpdk.org, "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [PATCH v2] devtools: fix error propagation from check-forbidden-tokens.awk
Date: Thu, 17 Jan 2019 13:20:20 +0100	[thread overview]
Message-ID: <CAJFAV8yf_Fi6bc0coUcCytTamhhQcQiequB2HTs73c_ho-qjRg@mail.gmail.com> (raw)
In-Reply-To: <18411484.mQl3YRKo9N@xps>

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 ?


-- 
David Marchand

  reply	other threads:[~2019-01-17 12:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 14:03 [PATCH v1] devtools: fix error propagation from check-forbidden-tokens.awk 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 ` [PATCH v2] " Arnon Warshavsky
2018-12-21  0:59   ` Thomas Monjalon
2019-01-17 12:20     ` David Marchand [this message]
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

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=CAJFAV8yf_Fi6bc0coUcCytTamhhQcQiequB2HTs73c_ho-qjRg@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=arnon@qwilt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.