From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 504094374A; Wed, 20 Dec 2023 14:37:14 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4A83640685; Wed, 20 Dec 2023 14:37:14 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id BAEAD402DD for ; Wed, 20 Dec 2023 14:37:12 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1703079432; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=H3yA2eEbRBfmZCOdeBidIi2VFAfFScRlOp94FM2513I=; b=KLCNZ5P8qpRcynU2BrpoJKfB0xgpxmyjuBPbgmWBpKSeGuC4mqgtTTkwCVFIODQrH9h0JH lqNP8kG1xBOM/j87MtuW2U6jukmkhUh5OpOTpJcyDVssiWNev4EsBpgFXrMGYtpfq7NIv4 16jvzjZFJ52NcnRry/45OAYfNef42Q0= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-591-kCVuB9YQNcmHhC91s6ABaA-1; Wed, 20 Dec 2023 08:37:09 -0500 X-MC-Unique: kCVuB9YQNcmHhC91s6ABaA-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id BB5EA85A58A; Wed, 20 Dec 2023 13:37:08 +0000 (UTC) Received: from RHTPC1VM0NT (unknown [10.22.32.214]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9EC18492BE6; Wed, 20 Dec 2023 13:37:07 +0000 (UTC) From: Aaron Conole To: Min Zhou Cc: ci@dpdk.org, msantana@redhat.com, dmarchan@redhat.com, thomas@monjalon.net, probb@iol.unh.edu, dceara@redhat.com, alialnu@nvidia.com Subject: Re: [PATCH v2] tools: fix parsing message-id in the headers of email References: <20231214024714.26763-1-zhoumin@loongson.cn> Date: Wed, 20 Dec 2023 08:37:04 -0500 In-Reply-To: <20231214024714.26763-1-zhoumin@loongson.cn> (Min Zhou's message of "Thu, 14 Dec 2023 02:47:14 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.10 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Min Zhou writes: > Some email has the message-id header named "Message-id", like this: > https://patches.dpdk.org/project/dpdk/patch/20230930010024.34377-1-rdna@apple.com/. > > This patch passes Message-[iI][dD] as the header argument to > getheader function. > > Acked-by: Aaron Conole > Signed-off-by: Min Zhou > --- Thanks, applied! > tools/parse-email.sh | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/tools/parse-email.sh b/tools/parse-email.sh > index 9cb9583..de8b5bb 100755 > --- a/tools/parse-email.sh > +++ b/tools/parse-email.sh > @@ -33,8 +33,7 @@ getheader () # > > subject=$(getheader Subject "$1") > from=$(getheader From "$1") > -msgid=$(getheader Message-Id "$1") > -[ -n "$msgid" ] || msgid=$(getheader Message-ID "$1") > +msgid=$(getheader Message-[iI][dD] "$1") > pwid=$(getheader X-Patchwork-Id "$1") > listid=$(getheader List-Id "$1") > reply=$(getheader In-Reply-To "$1")