From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [PATCH] devtools: add Co-developed-by to commit log check
Date: Thu, 12 Mar 2026 13:10:39 -0700 [thread overview]
Message-ID: <20260312131039.6ec4ddf3@phoenix.local> (raw)
In-Reply-To: <23032153.EfDdHjke4D@thomas>
On Thu, 12 Mar 2026 19:56:25 +0100
Thomas Monjalon <thomas@monjalon.net> wrote:
> 12/03/2026 19:54, Stephen Hemminger:
> > Add Co-developed-by to the recognized tag pattern and tag
> > sequence order in check-git-log.sh.
>
> Why using such tag? Signed-off-by is not enough?
>
>
The tags were inherited from the kernel development process.

Signed-off-by is the DCO (Developer Certificate of Origin) attestation.
It says "I certify that I have the right to submit this code under the project's license.
Co-developed-by explicitly marks someone as a co-author of the patch.
Without it, there's only one author recorded in the git metadata.
I just wanted check-git-log.sh to be quiet if it was used.
The Co-developed-by is new, and probably came about because some people
need/want to have their contributions recorded in the git statistics.
Silly corporate overlords count contributions and it matters to them...
PS: If DPDK was exactly following the kernel process, every time a patch was merged into a sub-tree
it would get a Signed-off-by from a maintainer. Because the maintainer is validating that
the submitter had the correct rights.
next prev parent reply other threads:[~2026-03-12 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 18:54 [PATCH] devtools: add Co-developed-by to commit log check Stephen Hemminger
2026-03-12 18:56 ` Thomas Monjalon
2026-03-12 20:10 ` Stephen Hemminger [this message]
2026-03-12 20:27 ` Thomas Monjalon
2026-03-12 22:46 ` Stephen Hemminger
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=20260312131039.6ec4ddf3@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.