Skip to contentSkip to conversation

docs/manual: patchwork is now at patchwork.buildroot.org

PATCH Applied Thomas Petazzoni via buildroot 2 participants 5 messages Aug 28 – Sep 4

lore
Share & tools
lore
#0 lore raw

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

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.

---
 docs/manual/contribute.adoc | 10 +++++-----
 docs/manual/resources.adoc  |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)
docs/manual/contribute.adoc +5 -5
index a0002ce188..f82eb14303 100644
@@ -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.
 
docs/manual/resources.adoc +1 -1
index a1b8b366e1..331929e0c6 100644
@@ -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/[].
Signature · 6 lines
2.55.0

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#1 lore raw

PATCH 2/2 docs/website: patchwork is now at patchwork.buildroot.org

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 website accordingly.

---
 docs/website/contribute.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
docs/website/contribute.html +1 -1
index c05bdda62d..8da371cf01 100644
@@ -18,7 +18,7 @@
 	    autobuild failures</a></li>
 	<li>Reviewing and testing patches sent by other developers. See the
 	  <a href="https://lists.buildroot.org/mailman/listinfo/buildroot">mailing list
-	  </a> or <a href="https://patchwork.ozlabs.org/project/buildroot/list/">
+	  </a> or <a href="https://patchwork.buildroot.org/project/buildroot/list/">
 	    patchwork</a>.</li>
 	<li>Working on items from the
 	  <a href="https://www.elinux.org/Buildroot#Todo_list">TODO list</a></li>
Signature · 6 lines
2.55.0

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#2 lore raw

Re: [Buildroot] [PATCH 2/2] docs/website: patchwork is now at patchwork.buildroot.org

Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thomas" == Thomas Petazzoni via buildroot <[email protected]> writes:

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 website accordingly.

Committed, thanks.

Signature · 5 lines
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#3 lore raw
In reply to Thomas Petazzoni via buildroot
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thomas" == Thomas Petazzoni via buildroot <[email protected]> writes:

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.

Committed, thanks.

Signature · 5 lines
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot
#4 lore raw
In reply to Thomas Petazzoni via buildroot

In reply of:

Quoted 5 lines

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.

Applied to 2025.02.x & 2026.05.x. Thanks

Quoted 59 lines
---
 docs/manual/contribute.adoc | 10 +++++-----
 docs/manual/resources.adoc  |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)
docs/manual/contribute.adoc +5 -5
index a0002ce188..f82eb14303 100644
@@ -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.
 
docs/manual/resources.adoc +1 -1
index a1b8b366e1..331929e0c6 100644
@@ -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/[].
Signature · 6 lines
2.55.0

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot