We don't actually list the mailing list address, just a link to mailman. The link to the Linux kernel patch submission guide should also be located here and not only in the README. Finally, a reference to the Github Actions is also appropriate. Signed-off-by: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> --- Documentation/user/introduction.rst | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/Documentation/user/introduction.rst b/Documentation/user/introduction.rst index 63a4c29cba67..d68b57e50333 100644 --- a/Documentation/user/introduction.rst +++ b/Documentation/user/introduction.rst @@ -21,7 +21,8 @@ Feedback -------- For sending patches, asking for help and giving general feedback you are -always welcome to write an e-mail to the barebox mailing list. Most of the +always welcome to write an e-mail to the barebox mailing list at +<mailto:barebox@xxxxxxxxxxxxxxxxxxx>. Most of the discussion of barebox takes place here: http://lists.infradead.org/mailman/listinfo/barebox/ @@ -29,10 +30,18 @@ http://lists.infradead.org/mailman/listinfo/barebox/ Mails sent to the barebox mailing list are archived on `lore.barebox.org <https://lore.barebox.org/barebox/>`_. +barebox uses a similar patch process as the Linux kernel, so most of the +`Linux guide for submitting patches <https://www.kernel.org/doc/html/latest/process/submitting-patches.html>`_ +also applies to barebox, except forthe need to select your recipient; +all barebox patches go to the same list. + Patch series sent there can be applied with `b4 <https://pypi.org/project/b4/>`_ :: git config b4.midmask https://lore.barebox.org/%s git config b4.linkmask https://lore.barebox.org/%s b4 shazam -M https://lore.barebox.org/$messageid # replace with link +CI tests are executed by Github Actions an be used by forking +`the project on Github <https://github.com/barebox/barebox>`. + There's also an IRC channel: #barebox on Libera Chat -- 2.39.2
