[Buildroot] [PATCH 1/2] docs/manual: patchwork is now at patchwork.buildroot.org

* [Buildroot] [PATCH 1/2] docs/manual: patchwork is now at patchwork.buildroot.org
@ 2026-08-28 17:19 Thomas Petazzoni via buildroot
  2026-08-28 17:20 ` [Buildroot] [PATCH 2/2] docs/website: " Thomas Petazzoni via buildroot
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Thomas Petazzoni via buildroot @ 2026-08-28 17:19 UTC (permalink / raw)
  To: buildroot; +Cc: Thomas Petazzoni

patchwork.buildroot.org used to be a redirect to patchwork.ozlabs.org,
but we are now running our own instance, so let's adjust the links in
the manual accordingly.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
 docs/manual/contribute.adoc | 10 +++++-----
 docs/manual/resources.adoc  |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/manual/contribute.adoc b/docs/manual/contribute.adoc
index a0002ce188..f82eb14303 100644
--- a/docs/manual/contribute.adoc
+++ b/docs/manual/contribute.adoc
@@ -460,7 +460,7 @@ editing the commit message. Below the +Signed-off-by+ section, add
 
 Although the changelog will be visible for the reviewers in the mail
 thread, as well as in
-https://patchwork.ozlabs.org/project/buildroot/list/[patchwork], +git+
+https://patchwork.buildroot.org/project/buildroot/list/[patchwork], +git+
 will automatically ignores lines below +---+ when the patch will be
 merged. This is the intended behavior: the changelog is not meant to
 be preserved forever in the +git+ history of the project.
@@ -513,19 +513,19 @@ $ git format-patch -v4 -M -s -o outgoing origin/master
 
 When you provide a new version of a patch, please mark the old one as
 superseded in
-https://patchwork.ozlabs.org/project/buildroot/list/[patchwork]. You
+https://patchwork.buildroot.org/project/buildroot/list/[patchwork]. You
 need to create an account on
-https://patchwork.ozlabs.org/project/buildroot/list/[patchwork] to be
+https://patchwork.buildroot.org/project/buildroot/list/[patchwork] to be
 able to modify the status of your patches. Note that you can only change
 the status of patches you submitted yourself, which means the email
 address you register in
-https://patchwork.ozlabs.org/project/buildroot/list/[patchwork] should
+https://patchwork.buildroot.org/project/buildroot/list/[patchwork] should
 match the one you use for sending patches to the mailing list.
 
 You can also add the +--in-reply-to=<message-id>+ option when
 submitting a patch to the mailing list. The id of the mail to reply to
 can be found under the "Message Id" tag on
-https://patchwork.ozlabs.org/project/buildroot/list/[patchwork]. The
+https://patchwork.buildroot.org/project/buildroot/list/[patchwork]. The
 advantage of *in-reply-to* is that patchwork will automatically mark
 the previous version of the patch as superseded.
 
diff --git a/docs/manual/resources.adoc b/docs/manual/resources.adoc
index a1b8b366e1..331929e0c6 100644
--- a/docs/manual/resources.adoc
+++ b/docs/manual/resources.adoc
@@ -68,4 +68,4 @@ review comments in a clean and concise web interface, it can be useful
 for all Buildroot developers.
 +
 The Buildroot patch management interface is available at
-https://patchwork.ozlabs.org/project/buildroot/list/[].
+https://patchwork.buildroot.org/project/buildroot/list/[].
-- 
2.55.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

^ permalink raw reply related	[flat|nested] 5+ messages in thread