DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Robin Jarry" <rjarry@redhat.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>, <dev@dpdk.org>
Cc: "Marat Khalili" <marat.khalili@huawei.com>
Subject: Re: [PATCH v3 1/2] devtools/mailmap_ctl: script to work with mailmap
Date: Fri, 17 Oct 2025 15:45:27 +0200	[thread overview]
Message-ID: <DDKN5IUVL6Y2.3MANZ0QIRGHUH@redhat.com> (raw)
In-Reply-To: <20251017133812.1109638-2-bruce.richardson@intel.com>

Bruce Richardson, Oct 17, 2025 at 15:38:
> Add a script to easily add entries to, check and sort the mailmap file.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Acked-by: Marat Khalili <marat.khalili@huawei.com>
> ---

Hey Bruce, I only have a couple of minor remarks:

$ isort --profile black --diff devtools/mailmap_ctl.py
--- devtools/mailmap_ctl.py:before	2025-10-17 15:42:59.507233
+++ devtools/mailmap_ctl.py:after	2025-10-17 15:43:03.351551
@@ -6,13 +6,13 @@
 A tool for manipulating the .mailmap file in DPDK repository.
 """

-import sys
-import re
 import argparse
 import itertools
+import re
+import sys
 import unicodedata
+from dataclasses import dataclass
 from pathlib import Path
-from dataclasses import dataclass


$ ruff check devtools/mailmap_ctl.py
devtools/mailmap_ctl.py:171:5: F841 Local variable `operations` is assigned to but never used
    |
169 |     """Main function."""
170 |     # ops and functions implementing them
171 |     operations = {"add": add_entry, "check": check_mailmap, "sort": sort_mailmap}
    |     ^^^^^^^^^^ F841
172 |
173 |     parser = argparse.ArgumentParser(
    |
    = help: Remove assignment to unused variable `operations`

Found 1 error.
No fixes available (1 hidden fix can be enabled with the `--unsafe-fixes` option).


With these fixed:

Reviewed-by: Robin Jarry <rjarry@redhat.com>

Thanks!

-- 
Robin

> 98% lean.


  reply	other threads:[~2025-10-17 13:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08 14:27 [PATCH 0/2] Improve mailmap file 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-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 [this message]
2025-10-17 14:05       ` Bruce Richardson
2025-10-17 13:38   ` [PATCH v3 2/2] mailmap: sort mailmap Bruce Richardson

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=DDKN5IUVL6Y2.3MANZ0QIRGHUH@redhat.com \
    --to=rjarry@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=marat.khalili@huawei.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).