From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Jeremy Plsek <jplsek@iol.unh.edu>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, "thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-ci] Moving tickets
Date: Tue, 11 Dec 2018 02:04:41 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0B9DEAAF@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CA+xUZB6Y=VPkGNFkNVXv8rijQrPUTtfYuRdqUYBtROx5SwKTnw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
Hi Jeremy,
I submitted a bug into Bugzilla, could you have a look at it ? https://bugs.dpdk.org/show_bug.cgi?id=122
Thanks
Lijuan
From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of Jeremy Plsek
Sent: Tuesday, December 11, 2018 12:47 AM
To: Yigit, Ferruh <ferruh.yigit@intel.com>
Cc: ci@dpdk.org; thomas@monjalon.net
Subject: Re: [dpdk-ci] Moving tickets
Yes, that's correct.
On Mon, Dec 10, 2018 at 8:26 AM Ferruh Yigit <ferruh.yigit@intel.com<mailto:ferruh.yigit@intel.com>> wrote:
On 12/7/2018 6:07 PM, Jeremy Plsek wrote:
> Hi all,
>
> I'll be moving most of the dashboard/ci/infrastructure related tickets from our
> internal Jira, to the bugzilla on Monday.
+1 to this, thanks!
I also assume new requests can be submit via bugzilla and you will be tracing
bugzilla for the new issues, is this correct?
>
> This is just a heads up, because unless some settings get changed, there will be
> a lot of new emails on Monday coming from this list.
>
> Thanks
> --
> Jeremy Plsek
> UNH InterOperability Laboratory
--
Jeremy Plsek
UNH InterOperability Laboratory
[-- Attachment #2: Type: text/html, Size: 5388 bytes --]
prev parent reply other threads:[~2018-12-11 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 18:07 Jeremy Plsek
2018-12-10 13:26 ` Ferruh Yigit
2018-12-10 16:46 ` Jeremy Plsek
2018-12-11 2:04 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0B9DEAAF@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=ci@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jplsek@iol.unh.edu \
--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).