Message ID | 20220615170854.3997869-1-fontaine.fabrice@gmail.com |
---|---|
State | Accepted |
Headers | show |
Series | [1/1] docs/manual: fix patchwork URL | expand |
On 15/06/2022 19:08, Fabrice Fontaine wrote: > 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> Applied to master, thanks. Regards, Arnout > --- > docs/manual/contribute.txt | 18 +++++++++++------- > docs/manual/resources.txt | 2 +- > 2 files changed, 12 insertions(+), 8 deletions(-) > > diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt > index bf2aed6b51..e588c69be6 100644 > --- a/docs/manual/contribute.txt > +++ b/docs/manual/contribute.txt > @@ -418,7 +418,8 @@ editing the commit message. Below the +Signed-off-by+ section, add > +---+ and your changelog. > > 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 > merged. This is the intended behavior: the changelog is not meant to > 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 > -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 > 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. > > 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 > -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 issues/bugs or getting help > diff --git a/docs/manual/resources.txt b/docs/manual/resources.txt > index e90a49b2ab..68b7eb9062 100644 > --- a/docs/manual/resources.txt > +++ b/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. > + > The Buildroot patch management interface is available at > -http://patchwork.buildroot.org[]. > +https://patchwork.ozlabs.org/project/buildroot/list/[].
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes: > On 15/06/2022 19:08, Fabrice Fontaine wrote: >> 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> > Applied to master, thanks. Committed to 2022.05.x and 2022.02.x, thanks.
diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt index bf2aed6b51..e588c69be6 100644 --- a/docs/manual/contribute.txt +++ b/docs/manual/contribute.txt @@ -418,7 +418,8 @@ editing the commit message. Below the +Signed-off-by+ section, add +---+ and your changelog. 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 merged. This is the intended behavior: the changelog is not meant to 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 -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 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. 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 -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 issues/bugs or getting help diff --git a/docs/manual/resources.txt b/docs/manual/resources.txt index e90a49b2ab..68b7eb9062 100644 --- a/docs/manual/resources.txt +++ b/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. + The Buildroot patch management interface is available at -http://patchwork.buildroot.org[]. +https://patchwork.ozlabs.org/project/buildroot/list/[].
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> --- docs/manual/contribute.txt | 18 +++++++++++------- docs/manual/resources.txt | 2 +- 2 files changed, 12 insertions(+), 8 deletions(-)