From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1355] Rename the execution section/stage
Date: Wed, 10 Jan 2024 10:26:15 +0000 [thread overview]
Message-ID: <bug-1355-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1355
Bug ID: 1355
Summary: Rename the execution section/stage
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: dts
Assignee: dev@dpdk.org
Reporter: juraj.linkes@pantheon.tech
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
The execution word/term is not the most fortunate as used in DTS, as it has a
pretty well established meaning outside of DTS. This creates confusion, so
let’s rename it to something better.
We should also agree on what do we call a full DTS run. That could just be a
DTS run. A part of the run (the current execution) could be a sub-run (a
sub-run would then be a testbed with testcases). Other possible words could be
job, testbed-run (the execution would be renamed to testbed in this case).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3045 bytes --]
reply other threads:[~2024-01-10 10:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1355-3@http.bugs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.