From: Thomas Monjalon <thomas@monjalon.net>
To: Jakub Palider <jpalider@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: [EXT] Re: [PATCH v2] devtools: ensure proper tag sequence
Date: Wed, 15 Jun 2022 20:58:27 +0200 [thread overview]
Message-ID: <3490937.iZASKD2KPV@thomas> (raw)
In-Reply-To: <PH0PR18MB45735A778D450E5498267760D5AD9@PH0PR18MB4573.namprd18.prod.outlook.com>
15/06/2022 10:46, Jakub Palider:
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Wednesday, June 15, 2022 8:21 AM
> > To: Jakub Palider <jpalider@marvell.com>
> > Cc: dev@dpdk.org; david.marchand@redhat.com
> > Subject: [EXT] Re: [PATCH v2] devtools: ensure proper tag sequence
> >
> > External Email
> >
> > ----------------------------------------------------------------------
> > 14/06/2022 00:21, jpalider@marvell.com:
> > > + SEQ[0] = "Coverity issue";
> > > + SEQ[1] = "Bugzilla ID";
> > > + SEQ[2] = "Fixes";
> > > + SEQ[3] = "Cc";
> > > + SEQ[4] = "^$";
> > > + SEQ[5] = "Suggested-by";
> > > + SEQ[6] = "Reported-by";
> > > + SEQ[7] = "Signed-off-by";
> > > + latest = 0;
> >
> > Do you think you could check that Review, Ack and Test are added after the
> > first Signed-off?
>
> Ok, thank you for clarification. So any further Signed-offs need not to be in a particular
> sequence as long as the first one precedes Review/Ack/Test (these 3 in any order).
Yes
> > > +Tag order
> > > +~~~~~~~~~
> > > +
> > > +There is a pattern indicating how certain tags should relate to each other.
> > > +
> > > +Example of proper tag sequence::
> > > +
> > > + Coverity issue:
> > > + Bugzilla ID:
> > > + Fixes:
> > > + Cc:
> > > +
> > > + Suggested-by:
> > > + Reported-by:
> > > + Signed-off-by:
> >
> > Given it is an example, you could add Reviewed-by, Acked-by and Tested-by.
>
> Sure, I will restore it.
>
> > > +
> > > +Between first and second tag section there is and empty line.
> > > +
> > > +While ``Signed-off-by:`` is an obligatory tag and must exists in each
> > > +commit, all other tags are optional. Any tag, as long as it is in
> > > +proper location to other adjacent tags (if present), may occur multiple
> > times.
> > > +
> > > +Other tags shall be laid out in a chronological order.
> >
> > Yes, after the first Signed-off-by.
>
> Side question: what about Sponsored-by, I noticed it appeared just recently?
It is a way to add the name of a company wishing to appear.
There is no constraint on it, it can be anywhere I think.
If it is in chronological order, it looks better before the Signed-off.
I think we should not advertise it here, because real names are more useful.
next prev parent reply other threads:[~2022-06-15 18:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 22:21 jpalider
2022-06-15 6:20 ` Thomas Monjalon
2022-06-15 8:46 ` [EXT] " Jakub Palider
2022-06-15 18:58 ` Thomas Monjalon [this message]
2022-07-19 12:01 ` [PATCH v3] " jpalider
2022-10-15 19:53 ` Jakub Palider
2022-11-25 9:56 ` Thomas Monjalon
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=3490937.iZASKD2KPV@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).