From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 663] Add In-Reply-To headers to report email
Date: Thu, 18 Mar 2021 15:09:49 +0000 [thread overview]
Message-ID: <bug-663-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=663
Bug ID: 663
Summary: Add In-Reply-To headers to report email
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: dashboard
Assignee: ci@dpdk.org
Reporter: blo@iol.unh.edu
CC: dpdklab@iol.unh.edu
Target Milestone: ---
Ferruh Yigit's email:
Another comment is, can we have "In-Reply-To:" headers in the lab reports, as
travis/checkpatch reports have it?
When I combine 'dev' and 'test-report' mail lists in to the same folder, when
report has "In-Reply-To:" headers, it is be displayed under the actual patch
and
easy to see/check the report details.
Without "In-Reply-To:" headers, it is very hard to find/see the test reports
unless you explicitly search for them.
A sample from travis report, for this patch, has following headers I mentioned:
In-Reply-To: <20210312110745.31721-10-ivan.malov@oktetlabs.ru>
References: <20210312110745.31721-10-ivan.malov@oktetlabs.ru>
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-03-18 15:09 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-663-149@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).