From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v4 0/2] improve mailmap file
Date: Thu, 23 Oct 2025 17:25:06 +0200 [thread overview]
Message-ID: <3958057.AxlXzFCzgd@thomas> (raw)
In-Reply-To: <20251020140805.1361249-1-bruce.richardson@intel.com>
20/10/2025 16:08, Bruce Richardson:
> The mailmap file in DPDK is not always correctly sorted, and standard
> cmdline sorting tools don't always do the job correctly. To improve
> things, add a new script to devtools for working with the mailmap file,
> to make it easier to add new entries in the correct place, to check the
> file for correctness, and lastly to sort the file in place (hopefully a
> one-off operation).
>
> Once that is done, commit the changes to the mailmap file to ensure it
> is correctly sorted in the repository.
>
> V4: minor changes based on more feedback:
> - sort imports alphabetically
> - remove unused "operations" map
>
> V3:
> * feedback from Robin's review:
> - used builtin type annotations
> - used argparse subparsers and callbacks for individual commands
> * re-sorted latest mailmap in patch 2
>
> V2:
> * address multiple feedback items on V1.
> * fix bug whereby adding an extra actually sorted the whole file
>
> Bruce Richardson (2):
> devtools/mailmap_ctl: script to work with mailmap
> mailmap: sort mailmap
>
> .mailmap | 356 ++++++++++++++++++++--------------------
> devtools/mailmap_ctl.py | 209 +++++++++++++++++++++++
For consistency, it should be named devtools/mailmap-ctl.py
Applied with this minor change, thanks.
prev parent reply other threads:[~2025-10-23 15:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 14:27 [PATCH 0/2] Improve " Bruce Richardson
2025-08-08 14:27 ` [PATCH 1/2] devtools/mailmap_ctl: script to work with mailmap Bruce Richardson
2025-08-08 16:44 ` Marat Khalili
2025-08-08 16:47 ` Bruce Richardson
2025-08-08 19:58 ` Bruce Richardson
2025-08-11 11:27 ` Marat Khalili
2025-08-08 14:27 ` [PATCH 2/2] mailmap: sort mailmap Bruce Richardson
2025-10-15 7:38 ` Varghese, Vipin
2025-10-15 7:41 ` Bruce Richardson
2025-10-21 4:01 ` Varghese, Vipin
2025-08-08 21:08 ` [PATCH v2 0/2] Improve mailmap file Bruce Richardson
2025-08-08 21:08 ` [PATCH v2 1/2] devtools/mailmap_ctl: script to work with mailmap Bruce Richardson
2025-08-11 11:28 ` Marat Khalili
2025-10-15 14:20 ` Robin Jarry
2025-10-17 13:35 ` Bruce Richardson
2025-08-08 21:08 ` [PATCH v2 2/2] mailmap: sort mailmap Bruce Richardson
2025-08-11 12:18 ` Marat Khalili
2025-10-17 13:38 ` [PATCH v3 0/2] Improve mailmap file Bruce Richardson
2025-10-17 13:38 ` [PATCH v3 1/2] devtools/mailmap_ctl: script to work with mailmap Bruce Richardson
2025-10-17 13:45 ` Robin Jarry
2025-10-17 14:05 ` Bruce Richardson
2025-10-17 13:38 ` [PATCH v3 2/2] mailmap: sort mailmap Bruce Richardson
2025-10-20 14:08 ` [PATCH v4 0/2] improve mailmap file Bruce Richardson
2025-10-20 14:08 ` [PATCH v4 1/2] devtools/mailmap_ctl: script to work with mailmap Bruce Richardson
2025-10-20 14:08 ` [PATCH v4 2/2] mailmap: sort mailmap Bruce Richardson
2025-10-23 15:25 ` Thomas Monjalon [this message]
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=3958057.AxlXzFCzgd@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).