From 1a5b1ce0722bfca256bf770b32370d4f2373e7e2 Mon Sep 17 00:00:00 2001 From: Neil Armstrong Date: Mon, 20 Jul 2026 10:23:30 +0200 Subject: doc: Migrate mailing-list to lists.u-boot-project.org 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 Signed-off-by: Neil Armstrong Reviewed-by: Peter Robinson --- doc/develop/security.rst | 2 +- doc/develop/sending_patches.rst | 12 ++++++------ 2 files changed, 7 insertions(+), 7 deletions(-) (limited to 'doc/develop') 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 -`u-boot@lists.denx.de` and use `scripts/get_maintainers.pl` to also include any +`u-boot@lists.u-boot-project.org` and use `scripts/get_maintainers.pl` to also include any relevant custodians. In addition, Tom Rini should be contacted at `trini@konsulko.com`. 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 -`_. U-Boot supports a huge amount of +`_. 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 `__ 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 ``u-boot@lists.denx.de`` and integrates with ``scripts/get_maintainer.pl`` +targets ``u-boot@lists.u-boot-project.org`` 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 ``u-boot@lists.denx.de``. +dispatching to ``u-boot@lists.u-boot-project.org``. .. 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 `u-boot@lists.denx.de - `_ mailing list. +* All patches must be sent to the `u-boot@lists.u-boot-project.org + `_ 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 -- cgit v1.3.1