From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] Your Bugzilla bug list needs attention.
Date: Wed, 20 Sep 2017 00:55:02 +0200 (CEST) [thread overview]
Message-ID: <20170919225503.092B5101B@dpdk.org> (raw)
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://dpdk.org/tracker/) that require
attention.
All of these bugs are in the CONFIRMED
state, and have not been touched in 7 days or more.
You need to take a look at them, and decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to
someone else. (Hint: if you don't know who to reassign it to, make
sure that the Component field seems reasonable, and then use the
"Reset Assignee to default" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Accept the bug by setting the status to IN_PROGRESS.
To get a list of all CONFIRMED bugs, you can use this URL (bookmark
it if you like!):
http://dpdk.org/tracker/buglist.cgi?bug_status=CONFIRMED&assigned_to=dev@dpdk.org
Or, you can use the general query page, at
http://dpdk.org/tracker/query.cgi
Appended below are the individual URLs to get to all of your CONFIRMED bugs
that haven't been touched for 7 days or more.
You will get this message once a day until you've dealt with these bugs!
Green goal: power efficiency with all hardwares
-> http://dpdk.org/tracker/show_bug.cgi?id=1
next reply other threads:[~2017-09-19 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 22:55 bugzilla [this message]
2019-06-20 11:45 bugzilla
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=20170919225503.092B5101B@dpdk.org \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).