[EXT] Re: [PATCH] devtools: ensure proper tag sequence
Jakub Palider
jpalider at marvell.com
Mon Jun 13 12:35:06 CEST 2022
> -----Original Message-----
> From: Thomas Monjalon <thomas at monjalon.net>
> Sent: Sunday, June 12, 2022 10:29 PM
> To: Jakub Palider <jpalider at marvell.com>
> Cc: dev at dpdk.org; david.marchand at redhat.com
> Subject: [EXT] Re: [PATCH] devtools: ensure proper tag sequence
>
> External Email
>
> ----------------------------------------------------------------------
> 12/06/2022 16:23, jpalider at marvell.com:
> > From: Jakub Palider <jpalider at marvell.com>
> >
> > This change to log checking procedure ensures that all
> > 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
>
> For the *-by sequence, the order is more chronological.
> Ack/Review/Test can be in any order I think.
>
>
Hi Thomas,
Do I get it right that the lines after <BLANK LINE> are fine in
current state and the patch could take care of the first section
only?
More information about the dev
mailing list