From: Quentin Schulz <[email protected]> The new domain needs /mailman added after the domain to be able to reach the mailman information page about the mailing list, so add it.
Signed-off-by: Quentin Schulz <[email protected]> --- doc/CONTRIBUTE.rst | 2 +- doc/develop/sending_patches.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/CONTRIBUTE.rst b/doc/CONTRIBUTE.rst index c7e5d9656c9a..e03945157029 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.u-boot-project.org/listinfo/u-boot>`_. +<https://lists.u-boot-project.org/mailman/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/develop/sending_patches.rst b/doc/develop/sending_patches.rst index 92c34c0669d0..a1e80eaff14c 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.u-boot-project.org/listinfo/u-boot>`_. U-Boot supports a huge amount of +<https://lists.u-boot-project.org/mailman/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, @@ -87,7 +87,7 @@ General Patch Submission Rules ------------------------------ * All patches must be sent to the `[email protected] - <https://lists.u-boot-project.org/listinfo/u-boot>`_ mailing list. + <https://lists.u-boot-project.org/mailman/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
