From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 229] lab scripts should be upstreamed to dpdk-ci repository
Date: Tue, 21 Apr 2020 13:57:05 +0000 [thread overview]
Message-ID: <bug-229-149-DIdgUL9mO7@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-229-149@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=229
Thomas Monjalon (thomas@monjalon.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
CC| |thomas@monjalon.net
Resolution|--- |DUPLICATE
--- Comment #3 from Thomas Monjalon (thomas@monjalon.net) ---
The scripts must be split to be easily consumable by any lab.
A new ticket is tracking the split effort: #451.
*** This bug has been marked as a duplicate of bug 451 ***
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2020-04-21 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 14:31 bugzilla
2020-04-21 13:57 ` bugzilla [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=bug-229-149-DIdgUL9mO7@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).