Re: [PATCH v4 2/3] doc: Migrate mailing-list to lists.u-boot-project.org

On Mon, 20 Jul 2026 at 09:23, Neil Armstrong <[email protected]> wrote:
>
> The U-Boot Mailing-list is moving to the lists.u-boot-project.org
> domain, so update all references of list.denx.de to the new
> domain in the documentation.
>
> Reviewed-by: Simon Glass <[email protected]>
> Signed-off-by: Neil Armstrong <[email protected]>
Reviewed-by: Peter Robinson <[email protected]>
> ---
>  doc/CONTRIBUTE.rst              |  4 ++--
>  doc/develop/security.rst        |  2 +-
>  doc/develop/sending_patches.rst | 12 ++++++------
>  doc/git-mailrc                  |  2 +-
>  doc/index.rst                   |  2 +-
>  5 files changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/doc/CONTRIBUTE.rst b/doc/CONTRIBUTE.rst
> index e8fa595ed4a..8494315254e 100644
> --- a/doc/CONTRIBUTE.rst
> +++ b/doc/CONTRIBUTE.rst
> @@ -28,7 +28,7 @@ Contributions
>
>  Contributions to the project are welcome. The U-Boot project uses a fairly
>  traditional Linux style development work-flow using git and `a mailing list
> -<https://lists.denx.de/listinfo/u-boot>`_.
> +<https://lists.u-boot-project.org/listinfo/u-boot>`_.
>
>  Patches should be sent to the mailing list using ``git send-email`` or the
>  equivalent commands using ``b4`` or ``patman`` with appropriate sign-off and
> @@ -41,7 +41,7 @@ The b4 tool automates a number of components mentioned above.
>  Code is not the only thing you can contribute to the project. As most
>  open-source projects, the U-Boot project suffers from a lack of reviewers.
>  Consider spending some time reading patches on `the mailing list archive
> -<https://lists.denx.de/pipermail/u-boot/>`_ and providing feedback to
> +<https://lists.u-boot-project.org/pipermail/u-boot/>`_ and providing feedback to
>  contributors when something could be improved or if you have questions. Contrary
>  to what's most often believed, you do not need to be an expert to review patches
>  and the project will benefit from people with different skillsets and experience
> 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..768c8375cf4 100644
> --- a/doc/develop/sending_patches.rst
> +++ b/doc/develop/sending_patches.rst
> @@ -5,7 +5,7 @@ Sending patches
>
>  *Before you begin* to implement any new ideas or concepts it is always a good
>  idea to present your plans on the `U-Boot mailing list
> -<https://lists.denx.de/listinfo/u-boot>`_. U-Boot supports a huge amount of
> +<https://lists.u-boot-project.org/listinfo/u-boot>`_. U-Boot supports a huge amount of
>  very different systems, and it is often impossible for the individual developer
>  to oversee the consequences of a specific change to all architectures.
>  Discussing concepts early can help you to avoid spending effort on code which,
> @@ -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,8 +86,8 @@ patman now lives outside the U-Boot tree; install it with
>  General Patch Submission Rules
>  ------------------------------
>
> -* All patches must be sent to the `[email protected]
> -  <https://lists.denx.de/listinfo/u-boot>`_ mailing list.
> +* All patches must be sent to the `[email protected]
> +  <https://lists.u-boot-project.org/listinfo/u-boot>`_ mailing list.
>
>  * If your patch affects the code maintained by one of the :ref:`custodians`, CC
>    them when emailing your patch. The easiest way to make sure you don't forget
> @@ -145,7 +145,7 @@ General Patch Submission Rules
>    If you believe you need to use a mailing list for testing (instead of any
>    regular mail address you own), we have a special test list for such purposes.
>    It would be best to subscribe to the list for the duration of your tests to
> -  avoid repeated moderation - see https://lists.denx.de/listinfo/test
> +  avoid repeated moderation - see https://lists.u-boot-project.org/listinfo/test
>
>  * Choose a meaningful Subject: - keep in mind that the Subject will also be
>    visible as headline of your commit message. Make sure the subject does not
> 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/doc/index.rst b/doc/index.rst
> index 5d732ff7a54..6fe8ca0788b 100644
> --- a/doc/index.rst
> +++ b/doc/index.rst
> @@ -9,7 +9,7 @@ This is the top level of the U-Boot's documentation tree.  U-Boot
>  documentation, like the U-Boot itself, is very much a work in progress;
>  that is especially true as we work to integrate our many scattered
>  documents into a coherent whole.  Please note that improvements to the
> -documentation are welcome; join the U-Boot list at http://lists.denx.de
> +documentation are welcome; join the U-Boot list at http://lists.u-boot-project.org
>  if you want to help out.
>
>  .. toctree::
>
> --
> 2.34.1
>