mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 2/3] Documentation: user: intro: add more info about mailing list
Date: Fri,  9 Aug 2024 16:24:43 +0200	[thread overview]
Message-ID: <20240809142444.316021-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20240809142444.316021-1-a.fatoum@pengutronix.de>

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@pengutronix.de>
---
 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@lists.infradead.org>. 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




  reply	other threads:[~2024-08-09 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09 14:24 [PATCH 1/3] Documentation: devel: background-execution: update section on I2C slices Ahmad Fatoum
2024-08-09 14:24 ` Ahmad Fatoum [this message]
2024-08-09 14:24 ` [PATCH 3/3] README: bring it up to date Ahmad Fatoum
2024-08-14  8:06   ` Sascha Hauer
2024-08-14  8:04 ` [PATCH 1/3] Documentation: devel: background-execution: update section on I2C slices Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240809142444.316021-2-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox