diff mbox

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

Message ID 1441627745-1553-1-git-send-email-Vincent.Riera@imgtec.com
State Superseded
Headers show

Commit Message

Vicente Olivert Riera Sept. 7, 2015, 12:09 p.m. UTC
Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
---
 docs/manual/contribute.txt |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

Comments

Arnout Vandecappelle Sept. 7, 2015, 12:15 p.m. UTC | #1
On 07-09-15 14:09, Vicente Olivert Riera wrote:
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>

Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

> ---
>  docs/manual/contribute.txt |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
> index 5f0762f..e24a0c5 100644
> --- a/docs/manual/contribute.txt
> +++ b/docs/manual/contribute.txt
> @@ -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

> +
>  [[reporting-bugs]]
>  === Reporting issues/bugs or getting help
>  
>
Thomas Petazzoni Sept. 7, 2015, 1:16 p.m. UTC | #2
Arnout, Vicente,

On Mon, 7 Sep 2015 14:15:58 +0200, Arnout Vandecappelle wrote:

> > +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
Vicente Olivert Riera Sept. 7, 2015, 1:21 p.m. UTC | #3
Dear Thomas Petazzoni,

On 09/07/2015 02:16 PM, Thomas Petazzoni wrote:
> Arnout, Vicente,
> 
> On Mon, 7 Sep 2015 14:15:58 +0200, Arnout Vandecappelle wrote:
> 
>>> +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'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/."

>  * 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.

> 
> Thomas
>
Arnout Vandecappelle Sept. 7, 2015, 2:11 p.m. UTC | #4
On 07-09-15 15:21, Vicente Olivert Riera wrote:
> Dear Thomas Petazzoni,
> 
> On 09/07/2015 02:16 PM, Thomas Petazzoni wrote:
>> Arnout, Vicente,
>>
>> On Mon, 7 Sep 2015 14:15:58 +0200, Arnout Vandecappelle wrote:
>>
>>>> +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'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/."

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

 Regards,
 Arnout

> 
>>  * 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.
> 
>>
>> Thomas
>>
Thomas Petazzoni Sept. 7, 2015, 9:01 p.m. UTC | #5
Vicente,

On Mon, 7 Sep 2015 14:21:40 +0100, Vicente Olivert Riera wrote:

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

> >  * 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
diff mbox

Patch

diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
index 5f0762f..e24a0c5 100644
--- a/docs/manual/contribute.txt
+++ b/docs/manual/contribute.txt
@@ -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