From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Aaron Conole <aconole@redhat.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [RFC] devtools: replace get-maintainer shell wrapper with Python script
Date: Sun, 01 Feb 2026 14:51:01 +0100 [thread overview]
Message-ID: <3273409.mvXUDI8C0e@thomas> (raw)
In-Reply-To: <20260131204823.29363-1-stephen@networkplumber.org>
31/01/2026 21:48, Stephen Hemminger:
> DPDK has been reusing the Linux kernel get_maintainer perl script
> but that creates an unwanted dependency on kernel source.
>
> This new script replaces that with a standalone Python implementation
> created in a few minutes with AI. The command line arguments are
> a subset of the features that make sense in DPDK.
Almost thousand lines for this new script.
Are you sure that's something we want to maintain ourself?
next prev parent reply other threads:[~2026-02-01 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 20:48 [RFC] devtools: replace get-maintainer shell wrapper with Python script Stephen Hemminger
2026-02-01 13:51 ` Thomas Monjalon [this message]
2026-02-01 19:01 ` Stephen Hemminger
2026-02-01 20:16 ` Thomas Monjalon
2026-02-01 22:23 ` Stephen Hemminger
2026-02-01 19:22 ` [RFC v2] devtools: replace checkpatches " Stephen Hemminger
2026-02-03 14:17 ` [RFC v3] " Stephen Hemminger
2026-02-04 16:59 ` [PATCH v4] " Stephen Hemminger
2026-02-04 17:29 ` Bruce Richardson
2026-02-04 17:32 ` Bruce Richardson
2026-02-05 1:43 ` Stephen Hemminger
2026-02-26 17:15 ` [PATCH v5] devtools: add Python-based patch style checker Stephen Hemminger
2026-03-24 14:48 ` [PATCH v6] " 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=3273409.mvXUDI8C0e@thomas \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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