Hi,

On 9/16/26 07:02, Mike Looijmans wrote:
The obsolete '[email protected]' address occurs in several places. Use
   sed s/[email protected]/[email protected]/g
so that patman and similar tools, as well as mortals, send their e-mails
to the correct mail list address.

already handled and merged with [1], your tree must be outdated.

Note we switched from master to main branch.

Neil

[1] 
https://lore.kernel.org/all/[email protected]/


Signed-off-by: Mike Looijmans <[email protected]>
---

  MAINTAINERS                     | 2 +-
  README                          | 6 +++---
  doc/develop/security.rst        | 2 +-
  doc/develop/sending_patches.rst | 6 +++---
  doc/git-mailrc                  | 2 +-
  tools/patman/settings.py        | 2 +-
  tools/u_boot_pylib/gitutil.py   | 2 +-
  7 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 45e9076de67..89a525631fa 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2050,7 +2050,7 @@ F:        test/py/tests/test_xxd/
THE REST
  M:    Tom Rini <[email protected]>
-L:     [email protected]
+L:     [email protected]
  Q:    http://patchwork.ozlabs.org/project/uboot/list/
  S:    Maintained
  T:    git https://source.denx.de/u-boot/u-boot.git
diff --git a/README b/README
index 5653f687e82..d77acc48999 100644
--- a/README
+++ b/README
@@ -45,9 +45,9 @@ Where to get help:
In case you have questions about, problems with or contributions for
  U-Boot, you should send a message to the U-Boot mailing list at
-<[email protected]>. There is also an archive of previous traffic
-on the mailing list - please search the archive before asking FAQ's.
-Please see https://lists.denx.de/pipermail/u-boot and
+<[email protected]>. There is also an archive of previous
+traffic on the mailing list - please search the archive before asking
+FAQ's. Please see https://lists.denx.de/pipermail/u-boot and
  https://marc.info/?l=u-boot
Where to get source code:
diff --git a/doc/develop/security.rst b/doc/develop/security.rst
index 84b130646f3..ed652ec756e 100644
--- a/doc/develop/security.rst
+++ b/doc/develop/security.rst
@@ -11,7 +11,7 @@ Contact
  -------
The preferred initial point of contact is to send email to
-`[email protected]` and use `scripts/get_maintainers.pl` to also include any
+`[email protected]` and use `scripts/get_maintainers.pl` to also 
include any
  relevant custodians. In addition, Tom Rini should be contacted at
  `[email protected]`.
diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
index c3e0ef27824..85b45e8f3a4 100644
--- a/doc/develop/sending_patches.rst
+++ b/doc/develop/sending_patches.rst
@@ -25,7 +25,7 @@ Using b4
  Use the `b4 <https://b4.docs.kernel.org/en/latest/>`__ tool to prepare and 
send
  your patches. b4 has become the preferred tool to sending patches for many 
Linux
  kernel contributors, and U-Boot ships with a ready-to-use ``.b4-config`` that
-targets ``[email protected]`` and integrates with 
``scripts/get_maintainer.pl``
+targets ``[email protected]`` and integrates with 
``scripts/get_maintainer.pl``
  for recipient discovery.
Start a topical series with ``b4 prep`` and keep the commits organised with
@@ -51,7 +51,7 @@ additional runs.
When the series is ready, use ``b4 send``. Begin with ``--dry-run`` to review the
  generated emails and ``--reflect`` to copy yourself for records before
-dispatching to ``[email protected]``.
+dispatching to ``[email protected]``.
.. code-block:: bash @@ -86,7 +86,7 @@ patman now lives outside the U-Boot tree; install it with
  General Patch Submission Rules
  ------------------------------
-* All patches must be sent to the `[email protected]
+* All patches must be sent to the `[email protected]
    <https://lists.denx.de/listinfo/u-boot>`_ mailing list.
* If your patch affects the code maintained by one of the :ref:`custodians`, CC
diff --git a/doc/git-mailrc b/doc/git-mailrc
index 65626d89eac..f0ba30a5c74 100644
--- a/doc/git-mailrc
+++ b/doc/git-mailrc
@@ -5,7 +5,7 @@
  # Then when sending patches, you can use:
  #     git send-email --to u-boot --cc i2c ...
-alias uboot [email protected]
+alias uboot  [email protected]
  alias u-boot uboot
# Maintainer aliases. Use the same alias here as patchwork to keep
diff --git a/tools/patman/settings.py b/tools/patman/settings.py
index 17229e0d823..fe65b1d3fb7 100644
--- a/tools/patman/settings.py
+++ b/tools/patman/settings.py
@@ -162,7 +162,7 @@ class _ProjectConfigParser(ConfigParser.ConfigParser):
  def ReadGitAliases(fname):
      """Read a git alias file. This is in the form used by git:
- alias uboot [email protected]
+    alias uboot  [email protected]
      alias wd     Wolfgang Denk <[email protected]>
Args:
diff --git a/tools/u_boot_pylib/gitutil.py b/tools/u_boot_pylib/gitutil.py
index 34b4dbb4839..59688aa7147 100644
--- a/tools/u_boot_pylib/gitutil.py
+++ b/tools/u_boot_pylib/gitutil.py
@@ -528,7 +528,7 @@ send --cc-cmd cc-fname" cover p1 p2'
                    "Please add something like this to a commit\n"
                    "Series-to: Fred Bloggs <[email protected]>\n"
                    "Or do something like this\n"
-                  "git config sendemail.to [email protected]")
+                  "git config sendemail.to [email protected]")
              return None
      cc = build_email_list(list(set(series.get('cc')) - set(series.get('to'))),
                            alias, '--cc', warn_on_error)
---
base-commit: ece349ade2973e220f524ce59e59711cc919263f
branch: maintainers


Reply via email to