[Buildroot] [PATCH] docs/manual: add the "mark as superseded" hint

[Buildroot] [PATCH] docs/manual: add the "mark as superseded" hint

[Vicente Olivert Riera]

Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
---
 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].
+
 [[reporting-bugs]]
 === Reporting issues/bugs or getting help
 
-- 
1.7.1

[Buildroot] [PATCH] docs/manual: add the "mark as superseded" hint

[Arnout Vandecappelle]

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

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

[Buildroot] [PATCH] docs/manual: add the "mark as superseded" hint

[Thomas Petazzoni]

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
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] [PATCH] docs/manual: add the "mark as superseded" hint

[Vicente Olivert Riera]

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
> 

[Buildroot] [PATCH] docs/manual: add the "mark as superseded" hint

[Arnout Vandecappelle]

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

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

[Buildroot] [PATCH] docs/manual: add the "mark as superseded" hint

[Thomas Petazzoni]

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
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com