public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/4] devtools: align trailer checks with kernel convention
Date: Thu,  2 Apr 2026 09:16:05 -0700	[thread overview]
Message-ID: <20260402161719.82570-1-stephen@networkplumber.org> (raw)

This series makes four incremental changes to check-git-log.sh to
align DPDK's commit message trailer handling with the Linux kernel
convention.

The motivation came from the recent work in kernel where the
same patch needed different trailer formatting for DPDK vs. the kernel.
This is unnecessary friction for developers who work across both
projects.

Patch 1: Use git's built-in %(trailers) format instead of grepping
  the commit body with hand-rolled patterns.

Patch 2: Recognize the kernel trailer tags that DPDK was missing:
  Co-developed-by, Closes:, and Link:.  Also adds proper format
  validation for Cc:, Coverity issue:, and Bugzilla ID: tags.

Patch 3: Remove the blank line requirement between relation tags
  (Fixes, Cc) and attribution tags (Signed-off-by).  All trailers
  now form a single contiguous block, matching kernel convention
  and git-interpret-trailers(1) semantics.

Patch 4: Demote tag ordering from error to warning, since the
  kernel itself does not enforce strict ordering via tooling.

Stephen Hemminger (4):
  devtools: use git trailer parser for tag extraction
  devtools: recognize kernel trailer tags
  devtools: remove blank line requirement between trailers
  devtools: demote tag ordering to warning

 devtools/check-git-log.sh | 50 +++++++++++++++++++++++----------------
 1 file changed, 29 insertions(+), 21 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-04-02 16:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02 16:16 Stephen Hemminger [this message]
2026-04-02 16:16 ` [RFC 3/4] devtools: remove blank line requirement between trailers Stephen Hemminger
2026-04-02 16:16 ` [RFC 4/4] devtools: demote tag ordering to warning 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=20260402161719.82570-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    /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