From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 144] [Epic] Add hardware description page
Date: Fri, 26 Apr 2019 20:29:35 +0000 [thread overview]
Message-ID: <bug-144-149-E4jHYwvlvk@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-144-149@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=144
Bug 144 depends on bug 147, which changed state.
Bug 147 Summary: Add jenkins information to hardware api
https://bugs.dpdk.org/show_bug.cgi?id=147
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--
You are receiving this mail because:
You are the assignee for the bug.
parent reply other threads:[~2019-04-26 20:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-144-149@http.bugs.dpdk.org/>]
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=bug-144-149-E4jHYwvlvk@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@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).