From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ci-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 204D6A0561
	for <public@inbox.dpdk.org>; Thu, 18 Mar 2021 16:09:51 +0100 (CET)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 06A0D406B4;
	Thu, 18 Mar 2021 16:09:51 +0100 (CET)
Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178])
 by mails.dpdk.org (Postfix) with ESMTP id D899340698
 for <ci@dpdk.org>; Thu, 18 Mar 2021 16:09:49 +0100 (CET)
Received: by inbox.dpdk.org (Postfix, from userid 33)
 id BA5B5A0562; Thu, 18 Mar 2021 16:09:49 +0100 (CET)
From: bugzilla@dpdk.org
To: ci@dpdk.org
Date: Thu, 18 Mar 2021 15:09:49 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: lab
X-Bugzilla-Component: dashboard
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: blo@iol.unh.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: ci@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter cc
 target_milestone
Message-ID: <bug-663-149@http.bugs.dpdk.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
Subject: [dpdk-ci] [Bug 663] Add In-Reply-To headers to report email
X-BeenThere: ci@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK CI discussions <ci.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/ci>,
 <mailto:ci-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/ci/>
List-Post: <mailto:ci@dpdk.org>
List-Help: <mailto:ci-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/ci>,
 <mailto:ci-request@dpdk.org?subject=subscribe>
Errors-To: ci-bounces@dpdk.org
Sender: "ci" <ci-bounces@dpdk.org>

https://bugs.dpdk.org/show_bug.cgi?id=3D663

            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=20
travis/checkpatch reports have it?

When I combine 'dev' and 'test-report' mail lists in to the same folder, wh=
en=20
report has "In-Reply-To:" headers, it is be displayed under the actual patch
and=20
easy to see/check the report details.

Without "In-Reply-To:" headers, it is very hard to find/see the test report=
s=20
unless you explicitly search for them.

A sample from travis report, for this patch, has following headers I mentio=
ned:
  In-Reply-To: <20210312110745.31721-10-ivan.malov@oktetlabs.ru>
  References: <20210312110745.31721-10-ivan.malov@oktetlabs.ru>

--=20
You are receiving this mail because:
You are the assignee for the bug.=