From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Dave Neary <dneary@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] thoughts on DPDK after a few days of reading sources
Date: Thu, 11 Feb 2016 17:20:57 +0100 [thread overview]
Message-ID: <7111981.Y5bUDIndo6@xps13> (raw)
In-Reply-To: <56BCB340.6040208@redhat.com>
2016-02-11 11:13, Dave Neary:
> Hi,
>
> On 02/11/2016 02:58 AM, Thomas Monjalon wrote:
> > 2016-02-10 19:05, Seth Arnold:
> > [...]
> >> It's nearly impossible to solve issues without error reporting. Good
> >> error reporting saves admins time and money.
> >
> > Until now, the errors were reported on the list and most often fixed quickly.
> > While I agree we need a more formal process (a bug tracker), I think we must
> > be noticed of new bugs on the mailing list.
> > Since nobody was against the bugzilla proposal, a deployment will be planned.
> > http://dpdk.org/ml/archives/dev/2015-August/023012.html
>
> I may have misunderstood Seth's comment, but it looked like he was
> talking about checking errno after fopen and reporting the error with
> perror or strerror in the event of a non-zero return.
Maybe I misunderstood his comments.
Anyway, after looking at his list of bugs, it appears that a bug tracker
would be useful :)
next prev parent reply other threads:[~2016-02-11 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 3:05 Seth Arnold
2016-02-11 3:41 ` Matthew Hall
2016-02-11 7:58 ` Thomas Monjalon
2016-02-11 11:58 ` Alejandro Lucero
2016-02-17 9:35 ` Christian Ehrhardt
2016-02-11 16:13 ` Dave Neary
2016-02-11 16:20 ` Thomas Monjalon [this message]
2016-02-11 16:29 ` Wiles, Keith
2016-02-15 10:36 ` Christian Ehrhardt
2016-02-11 22:48 ` Stephen Hemminger
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=7111981.Y5bUDIndo6@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=dneary@redhat.com \
/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).