DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: jpalider@marvell.com
Cc: david.marchand@redhat.com, dev@dpdk.org
Subject: Re: [PATCH v3] devtools: ensure proper tag sequence
Date: Fri, 25 Nov 2022 10:56:56 +0100	[thread overview]
Message-ID: <1720496.X513TT2pbd@thomas> (raw)
In-Reply-To: <20220719120123.3786204-1-jpalider@marvell.com>

19/07/2022 14:01, jpalider@marvell.com:
> From: Jakub Palider <jpalider@marvell.com>
> 
> This change to log checking procedure ensures that certain
> tags are in proper order.
> The order of tags is as follows:
>  * Coverity issue
>  * Bugzilla ID
>  * Fixes
>  * Cc
>  * <BLANK LINE>
>  * Suggested-by
>  * Reported-by
>  + Signed-off-by
>  * Acked-by
>  * Reviewed-by
>  * Tested-by
> where:
>  * => 0 or more than one instance possible
>  + => more than once instance possible
> In order to satisfy the above requirements an extra check
> is performed for obligatory tags.
> 
> v3:
> * restored some tags under check
> * defined chronological order after Signed-off
> 
> v2:
> * narrowed down the tags under check
> 
> Signed-off-by: Jakub Palider <jpalider@marvell.com>

I've moved "Reported-by" before "Suggested-by" and
made the output more consistent with other checks.

Applied, thanks.




      parent reply	other threads:[~2022-11-25  9:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 22:21 [PATCH v2] " jpalider
2022-06-15  6:20 ` Thomas Monjalon
2022-06-15  8:46   ` [EXT] " Jakub Palider
2022-06-15 18:58     ` Thomas Monjalon
2022-07-19 12:01 ` [PATCH v3] " jpalider
2022-10-15 19:53   ` Jakub Palider
2022-11-25  9:56   ` Thomas Monjalon [this message]

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=1720496.X513TT2pbd@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jpalider@marvell.com \
    /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).