[PATCH RFC v2 2/4] doc: Migrate mailing-list to lists.u-boot-project.org
Neil Armstrong
neil.armstrong at linaro.org
Tue Jun 23 15:22:25 CEST 2026
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.
The URLs were manually updated since the mailman links don't
match anymore after the archive import in the new mailman instance.
Signed-off-by: Neil Armstrong <neil.armstrong at linaro.org>
---
doc/CONTRIBUTE.rst | 2 +-
doc/chromium/chainload.rst | 4 ++--
doc/develop/codingstyle.rst | 4 ++--
doc/develop/historical/generic_board.rst | 6 +++---
doc/develop/security.rst | 2 +-
doc/develop/sending_patches.rst | 8 ++++----
doc/git-mailrc | 2 +-
doc/index.rst | 2 +-
8 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/doc/CONTRIBUTE.rst b/doc/CONTRIBUTE.rst
index a6e1cd1fb68..9777383f245 100644
--- a/doc/CONTRIBUTE.rst
+++ b/doc/CONTRIBUTE.rst
@@ -29,7 +29,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
diff --git a/doc/chromium/chainload.rst b/doc/chromium/chainload.rst
index b00ee94eaa4..c396073001e 100644
--- a/doc/chromium/chainload.rst
+++ b/doc/chromium/chainload.rst
@@ -42,9 +42,9 @@ Nyan-big
Compiled based on information here::
- https://lists.denx.de/pipermail/u-boot/2015-March/209530.html
+ https://lists.u-boot-project.org/pipermail/u-boot/2015-March/208951.html
https://git.collabora.com/cgit/user/tomeu/u-boot.git/commit/?h=nyan-big
- https://lists.denx.de/pipermail/u-boot/2017-May/289491.html
+ https://lists.u-boot-project.org/pipermail/u-boot/2017-May/288915.html
https://github.com/chromeos-nvidia-androidtv/gnu-linux-on-acer-chromebook-13#copy-data-to-the-sd-card
1. Build U-Boot
diff --git a/doc/develop/codingstyle.rst b/doc/develop/codingstyle.rst
index 26881cf3900..a7230a0e364 100644
--- a/doc/develop/codingstyle.rst
+++ b/doc/develop/codingstyle.rst
@@ -29,7 +29,7 @@ The following rules apply:
* 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 ``u-boot at lists.denx.de`` and integrates with ``scripts/get_maintainer.pl`` for
+ targets ``u-boot at 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
@@ -55,7 +55,7 @@ The following rules apply:
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 at lists.denx.de``.
+ dispatching to ``u-boot at lists.u-boot-project.org``.
.. code-block:: bash
diff --git a/doc/develop/historical/generic_board.rst b/doc/develop/historical/generic_board.rst
index 12550a140e0..bf4bb25cf92 100644
--- a/doc/develop/historical/generic_board.rst
+++ b/doc/develop/historical/generic_board.rst
@@ -64,17 +64,17 @@ separate function calls so that they can easily be included or excluded
for a particular architecture. It also makes it easier to adopt Graeme's
initcall proposal when it is ready.
-http://lists.denx.de/pipermail/u-boot/2012-January/114499.html
+http://lists.u-boot-project.org/pipermail/u-boot/2012-January/114135.html
This series removes the dependency on generic relocation. So relocation
happens as one big chunk and is still completely arch-specific. See the
relocation series for a proposed solution to this for ARM:
-http://lists.denx.de/pipermail/u-boot/2011-December/112928.html
+http://lists.u-boot-project.org/pipermail/u-boot/2011-December/112165.html
or Graeme's recent x86 series v2:
-http://lists.denx.de/pipermail/u-boot/2012-January/114467.html
+http://lists.u-boot-project.org/pipermail/u-boot/2012-January/114103.html
Instead of moving over a whole architecture, this series takes the approach
of simply enabling generic board support for an architecture. It is then up
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 at lists.denx.de` and use `scripts/get_maintainers.pl` to also include any
+`u-boot at 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 at konsulko.com`.
diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
index e29fa175727..4ac820ec78f 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,
@@ -29,8 +29,8 @@ See more details at :doc:`patman`.
General Patch Submission Rules
------------------------------
-* All patches must be sent to the `u-boot at lists.denx.de
- <https://lists.denx.de/listinfo/u-boot>`_ mailing list.
+* All patches must be sent to the `u-boot at lists.u-boot-project.org
+ <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
@@ -88,7 +88,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 u-boot at lists.denx.de
+alias uboot u-boot at lists.u-boot-project.org
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
More information about the U-Boot
mailing list