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 master 1/2] Documentation: user: intro: update feedback section on ML
Date: Thu, 20 Mar 2025 09:24:25 +0100	[thread overview]
Message-ID: <20250320082426.2124644-1-a.fatoum@pengutronix.de> (raw)

Now that kernel.org also mirrors barebox, we don't require the midmask,
linkmask configuration we had before.

Adapt the docs accordingly and explain shazam -H a bit.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/user/introduction.rst | 21 +++++++++++++--------
 1 file changed, 13 insertions(+), 8 deletions(-)

diff --git a/Documentation/user/introduction.rst b/Documentation/user/introduction.rst
index d68b57e50333..7cd289d73e39 100644
--- a/Documentation/user/introduction.rst
+++ b/Documentation/user/introduction.rst
@@ -22,26 +22,31 @@ 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 at
-<mailto:barebox@lists.infradead.org>. Most of the
-discussion of barebox takes place here:
+`barebox@lists.infradead.org <mailto:barebox@lists.infradead.org>`_.
+Most of the discussion of barebox takes place here:
 
 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/>`_.
+`lore.barebox.org <https://lore.barebox.org/barebox/>`_ and
+`lore.kernel.org <https://lore.kernel.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;
+also applies to barebox, except for the 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/>`_ ::
+Patch series can be sent and fetched from the list using `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
+Fixes should apply on master and new features on the next branch.
+If a series fails to apply, ``b4`` can determine/guess the base
+and have ``FETCH_HEAD`` point at it::
+
+   b4 shazam -H https://lore.kernel.org/$messageid # URL can be omitted
+
+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: #barebox on Libera Chat
-- 
2.39.5




             reply	other threads:[~2025-03-20  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20  8:24 Ahmad Fatoum [this message]
2025-03-20  8:24 ` [PATCH master 2/2] Revert "Documentation: remove info about bridging to matrix" Ahmad Fatoum
2025-03-20 11:45 ` [PATCH master 1/2] Documentation: user: intro: update feedback section on ML 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=20250320082426.2124644-1-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