浏览代码

docs/manual: fix patchwork URL

http://patchwork.buildroot.org is redirecting to
https://bugs.busybox.net so replace it by
https://patchwork.ozlabs.org/project/buildroot/list/ as already done in
docs/website/contribute.html

Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
(cherry picked from commit 002f0e927d857e51595cedf3d2a44613b4f7e5f1)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Fabrice Fontaine 3 年之前
父节点
当前提交
2f2eb49376
共有 2 个文件被更改,包括 12 次插入8 次删除
  1. 11 7
      docs/manual/contribute.txt
  2. 1 1
      docs/manual/resources.txt

+ 11 - 7
docs/manual/contribute.txt

@@ -418,7 +418,8 @@ editing the commit message. Below the +Signed-off-by+ section, add
 +---+ and your changelog.
 +---+ and your changelog.
 
 
 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 http://patchwork.buildroot.org[patchwork], +git+
+thread, as well as in
+https://patchwork.ozlabs.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.
@@ -470,19 +471,22 @@ $ 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 http://patchwork.buildroot.org[patchwork]. You need to
-create an account on http://patchwork.buildroot.org[patchwork] to be
+superseded in
+https://patchwork.ozlabs.org/project/buildroot/list/[patchwork]. You
+need to create an account on
+https://patchwork.ozlabs.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 http://patchwork.buildroot.org[patchwork] should
+address you register in
+https://patchwork.ozlabs.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
-http://patchwork.buildroot.org[patchwork].  The advantage of
-*in-reply-to* is that patchwork will automatically mark the previous
-version of the patch as superseded.
+https://patchwork.ozlabs.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.
 
 
 [[reporting-bugs]]
 [[reporting-bugs]]
 === Reporting issues/bugs or getting help
 === Reporting issues/bugs or getting help

+ 1 - 1
docs/manual/resources.txt

@@ -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
-http://patchwork.buildroot.org[].
+https://patchwork.ozlabs.org/project/buildroot/list/[].