From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: add the "mark as superseded" hint
Date: Mon, 7 Sep 2015 14:21:40 +0100 [thread overview]
Message-ID: <55ED8F64.5080706@imgtec.com> (raw)
In-Reply-To: <20150907151606.6e6357f4@free-electrons.com>
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
>
next prev parent reply other threads:[~2015-09-07 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 12:09 [Buildroot] [PATCH] docs/manual: add the "mark as superseded" hint Vicente Olivert Riera
2015-09-07 12:15 ` Arnout Vandecappelle
2015-09-07 13:16 ` Thomas Petazzoni
2015-09-07 13:21 ` Vicente Olivert Riera [this message]
2015-09-07 14:11 ` Arnout Vandecappelle
2015-09-07 21:01 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55ED8F64.5080706@imgtec.com \
--to=vincent.riera@imgtec.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.