From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH v2 3/4] Documentation: user: split community from feedback
Date: Fri, 11 Jul 2025 09:32:07 +0200 [thread overview]
Message-ID: <20250711073208.3926688-4-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20250711073208.3926688-1-a.fatoum@pengutronix.de>
Place the Matrix/IRC links more prominently by moving them above the
information for how to send patches.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
v1 -> v2:
- new patch
---
Documentation/user/introduction.rst | 19 ++++++++++++-------
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git a/Documentation/user/introduction.rst b/Documentation/user/introduction.rst
index cba1d09986b8..5b2a39f3c5c3 100644
--- a/Documentation/user/introduction.rst
+++ b/Documentation/user/introduction.rst
@@ -15,10 +15,10 @@ development binary as well as for lean production systems.
Just like busybox is the Swiss Army Knife for embedded Linux,
barebox is the Swiss Army Knife for bare metal, hence the name.
-.. _feedback:
+.. _community:
-Feedback
---------
+Community
+---------
For sending patches, asking for help and giving general feedback you are
always welcome to write an e-mail to the barebox mailing list at
@@ -31,6 +31,15 @@ Mails sent to the barebox mailing list are archived on
`lore.barebox.org <https://lore.barebox.org/barebox/>`_ and
`lore.kernel.org <https://lore.kernel.org/barebox/>`_.
+There's also an IRC channel, which is
+`bridged to Matrix <https://app.element.io/#/room/#barebox:matrix.org>`_:
+#barebox on Libera Chat.
+
+.. _feedback:
+
+Sending Patches
+---------------
+
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 for the need to select your recipient;
@@ -48,7 +57,3 @@ and have ``FETCH_HEAD`` point at it::
CI tests are executed by Github Actions can be used by forking
`the project on Github <https://github.com/barebox/barebox>`.
-
-There's also an IRC channel, which is
-`bridged to Matrix <https://app.element.io/#/room/#barebox:matrix.org>`_:
-#barebox on Libera Chat.
--
2.39.5
next prev parent reply other threads:[~2025-07-11 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 7:32 [PATCH v2 0/4] Documentation: devel: add new troubleshooting Ahmad Fatoum
2025-07-11 7:32 ` [PATCH v2 1/4] Documentation: devel: porting: split out architecture intro Ahmad Fatoum
2025-07-11 7:32 ` [PATCH v2 2/4] Documentation: devel: architecture: detail first/second stage handling Ahmad Fatoum
2025-07-11 7:32 ` Ahmad Fatoum [this message]
2025-07-11 7:32 ` [PATCH v2 4/4] Documentation: devel: troubleshooting: add new chapter Ahmad Fatoum
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=20250711073208.3926688-4-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