Skip to contentSkip to conversation

docs/manual: add the "mark as superseded" hint

PATCH Superseded Vicente Olivert Riera 3 participants 6 messages Sep 7, 2015

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 docs/manual: add the "mark as superseded" hint

---
 docs/manual/contribute.txt |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)
docs/manual/contribute.txt +3 -0
index 5f0762f..e24a0c5 100644
@@ -298,6 +298,9 @@ $ git format-patch --subject-prefix "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].
+
 [[reporting-bugs]]
 === Reporting issues/bugs or getting help
 
Signature · 1 line
1.7.1
#1 lore raw

PATCH 1/1 docs/manual: add the "mark as superseded" hint

Quoted 1 line · Vicente Olivert Riera
Quoted 9 lines
---
 docs/manual/contribute.txt |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)
docs/manual/contribute.txt +0 -0
index 5f0762f..e24a0c5 100644

docs/manual/contribute.txt $ git format-patch --subject-prefix "PATCH v4" \ · line 302

Quoted 5 lines
docs/manual/contribute.txt +2 -0
@@ -298,6 +298,9 @@ $ git format-patch --subject-prefix "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].

It may be useful to add that it's necessary to create an account to be able to
do that:

You need to create an account on patchwork to be able to modify the status of your patches. Note that you can only change the status of patches you submitted yourself.

Regards,
Arnout

Quoted 5 lines
docs/manual/contribute.txt +1 -0
+
 [[reporting-bugs]]
 === Reporting issues/bugs or getting help
 
Signature · 6 lines
Arnout Vandecappelle      arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
#2 lore raw

PATCH 1/1 docs/manual: add the "mark as superseded" hint

Arnout, Vicente,

Quoted 9 lines · Arnout Vandecappelle

docs/manual/contribute.txt $ git format-patch --subject-prefix "PATCH v4" \ · line 302

Quoted 2 lines
docs/manual/contribute.txt +2 -0
+When you provide a new version of a patch, please mark the old one as
+superseded in http://patchwork.buildroot.org[patchwork].

It may be useful to add that it's necessary to create an account to be able to
do that:

You need to create an account on patchwork to be able to modify the status of your patches. Note that you can only change the status of patches you submitted yourself.

And:

* More generally explain what is patchwork, and what it is doing
* That the account must be created with an e-mail address matching the one used to submit the patches

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
#3 lore raw

PATCH 1/1 docs/manual: add the "mark as superseded" hint

Dear Thomas Petazzoni,

Quoted 10 lines · Thomas Petazzoni

Arnout, Vicente,

Quoted 6 lines · Arnout Vandecappelle

docs/manual/contribute.txt $ git format-patch --subject-prefix "PATCH v4" \ · line 302

Quoted 2 lines
docs/manual/contribute.txt +2 -0
+When you provide a new version of a patch, please mark the old one as
+superseded in http://patchwork.buildroot.org[patchwork].

It may be useful to add that it's necessary to create an account to be able to
do that:

Quoted 7 lines
Quoted 3 lines

You need to create an account on patchwork to be able to modify the status of your patches. Note that you can only change the status of patches you submitted yourself.

And:

* More generally explain what is patchwork, and what it is doing

That's already included in the manual. See:

"Patchwork

Patchwork is a web-based patch tracking system designed to
facilitate the contribution and management of contributions to an open-source project. Patches that have been sent to a mailing list are 'caught' by the system, and appear on a web page. Any comments posted that reference the patch are appended to the patch page too. For more information on Patchwork see http://jk.ozlabs.org/projects/patchwork/."

Quoted 2 lines

* That the account must be created with an e-mail address matching the one used to submit the patches

Already included in v2:

http://patchwork.ozlabs.org/patch/515116/

Regards,

Vincent.

Quoted 3 lines

Thomas

#4 lore raw

PATCH 1/1 docs/manual: add the "mark as superseded" hint

Quoted 23 lines · Vicente Olivert Riera

Dear Thomas Petazzoni,

Quoted 10 lines · Thomas Petazzoni

Arnout, Vicente,

Quoted 6 lines · Arnout Vandecappelle

docs/manual/contribute.txt $ git format-patch --subject-prefix "PATCH v4" \ · line 302

Quoted 2 lines
docs/manual/contribute.txt +2 -0
+When you provide a new version of a patch, please mark the old one as
+superseded in http://patchwork.buildroot.org[patchwork].

It may be useful to add that it's necessary to create an account to be able to
do that:

Quoted 7 lines
Quoted 3 lines

You need to create an account on patchwork to be able to modify the status of your patches. Note that you can only change the status of patches you submitted yourself.

And:

* More generally explain what is patchwork, and what it is doing

That's already included in the manual. See:

Quoted 8 lines

"Patchwork

Patchwork is a web-based patch tracking system designed to
facilitate the contribution and management of contributions to an open-source project. Patches that have been sent to a mailing list are 'caught' by the system, and appear on a web page. Any comments posted that reference the patch are appended to the patch page too. For more information on Patchwork see http://jk.ozlabs.org/projects/patchwork/."

BTW, I considered asking to add a link to that section, but in the end decided
it's not very useful.

Regards,
Arnout

Quoted 15 lines
Quoted 3 lines

* That the account must be created with an e-mail address matching the one used to submit the patches

Already included in v2:

http://patchwork.ozlabs.org/patch/515116/

Regards,

Vincent.

Quoted 3 lines

Thomas

Signature · 6 lines
Arnout Vandecappelle      arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium . . . . . BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
#5 lore raw

PATCH 1/1 docs/manual: add the "mark as superseded" hint

In reply to Vicente Olivert Riera

Vicente,

Quoted 10 lines · Vicente Olivert Riera

That's already included in the manual. See:

"Patchwork

Patchwork is a web-based patch tracking system designed to
facilitate the contribution and management of contributions to an open-source project. Patches that have been sent to a mailing list are 'caught' by the system, and appear on a web page. Any comments posted that reference the patch are appended to the patch page too. For more information on Patchwork see http://jk.ozlabs.org/projects/patchwork/."

Alright, that's good. I forgot about this.

Quoted 6 lines
Quoted 2 lines

* That the account must be created with an e-mail address matching the one used to submit the patches

Already included in v2:

http://patchwork.ozlabs.org/patch/515116/

Great, thanks a lot!

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com