mirror/buildroot
1
0
Fork 0
mirror of https://gitlab.com/buildroot.org/buildroot.git synced 2026-09-30 22:11:59 -09:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source 
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>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
(cherry picked from commit 2d7d9d8200)
Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>
This commit is contained in:
Thomas Petazzoni
2026-08-28 19:19:59 +02:00
committed by Raphaël Mélotte
parent 8e44aff085
commit 421c616bf8
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/manual/contribute.adoc
View File

@@ -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 Although the changelog will be visible for the reviewers in the mail
thread, as well as in 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 will automatically ignores lines below +---+ when the patch will be
merged. This is the intended behavior: the changelog is not meant to merged. This is the intended behavior: the changelog is not meant to
be preserved forever in the +git+ history of the project. 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 When you provide a new version of a patch, please mark the old one as
superseded in 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 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 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 the status of patches you submitted yourself, which means the email
address you register in 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. match the one you use for sending patches to the mailing list.
You can also add the +--in-reply-to=<message-id>+ option when 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 submitting a patch to the mailing list. The id of the mail to reply to
can be found under the "Message Id" tag on 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 advantage of *in-reply-to* is that patchwork will automatically mark
the previous version of the patch as superseded. the previous version of the patch as superseded.

2
docs/manual/resources.adoc
View File

@@ -68,4 +68,4 @@ review comments in a clean and concise web interface, it can be useful
for all Buildroot developers. for all Buildroot developers.
+ +
The Buildroot patch management interface is available at The Buildroot patch management interface is available at
https://patchwork.ozlabs.org/project/buildroot/list/[]. https://patchwork.buildroot.org/project/buildroot/list/[].