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 8457D42882; Fri, 31 Mar 2023 12:37:50 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0E8DB42C76; Fri, 31 Mar 2023 12:37:50 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 2649142BC9 for ; Fri, 31 Mar 2023 12:37:48 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680259067; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yCVquX+QBe7xr1z1+07FYosoXwrijavunubMrYszIFg=; b=FqHM4Xl5fwOPVP9FbY5rJcbLWe54teERtBtO602mba0cuEa6z5Q8vkJsywOXl9XpnhoyEh VNugI6jEZ1WZtIGAR/zjR9dNWbx7RHIXKhxBxMnNvUER9tPDr5E00ZsMzc7pNm7X1SYcJb q1YecpR4vx1PhszqF5b3bBBPuCruOrU= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-218-Q69KHmwCNcS4U5eMN4hYqg-1; Fri, 31 Mar 2023 06:37:44 -0400 X-MC-Unique: Q69KHmwCNcS4U5eMN4hYqg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E15BE886463; Fri, 31 Mar 2023 10:37:43 +0000 (UTC) Received: from [10.39.208.19] (unknown [10.39.208.19]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 545FC4042AC0; Fri, 31 Mar 2023 10:37:42 +0000 (UTC) Message-ID: Date: Fri, 31 Mar 2023 12:37:40 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH] doc: relax requirement on commit messages of security fixes To: Thomas Monjalon , dev@dpdk.org Cc: david.marchand@redhat.com, ktraynor@redhat.com, Luca Boccassi , luca.boccassi@gmail.com, Christian Ehrhardt , xuemingl@nvidia.com References: <20220310175947.273850-1-luca.boccassi@gmail.com> <5508921.CQOukoFCf9@thomas> From: Maxime Coquelin In-Reply-To: <5508921.CQOukoFCf9@thomas> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Indeed! On 3/31/23 12:34, Thomas Monjalon wrote: > We missed this patch, there was no comment. > Please review. > > 10/03/2022 18:59, luca.boccassi@gmail.com: >> From: Luca Boccassi >> >> Allow more flexibility with embargo lifting by not requiring >> mentions of CVEs in commit messages if the lift date allows >> it. >> >> Signed-off-by: Luca Boccassi >> --- >> -The CVE id and the bug id must be referenced in the patch. >> +The CVE id and the bug id must be referenced in the patch if there is no >> +embargo, or if there is an embargo, but it will be lifted when the release >> +including the patch is published. If the embargo is going to be lifted after the >> +release, then the CVE and bug ids must be omitted from the commit message. > > Reviewed-by: Maxime Coquelin Thanks, Maxime