From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: announce@dpdk.org
Subject: [dpdk-announce] patchwork available
Date: Thu, 02 Oct 2014 16:26:12 +0200 [thread overview]
Message-ID: <2894525.Uqi71VIjsf@xps13> (raw)
Hi all,
A tool is now available to check state of the patches:
http://dpdk.org/dev/patchwork
It also helps to download patches for testing/review.
Some explanations can be found in the dev page:
http://dpdk.org/dev#patchwork
Mails are automatically added to patchwork's database but every other actions
are manual. It is possible to setup some scripts to automate more things but
it would fail in many cases and would make it unreliable.
So, in order to ease the maintenance of this database, developers are now
responsible of obsoleting patches when they send a new version of a patch.
In other words, please set your v1 patch as "Superseded" when sending a v2.
Thanks
--
Thomas
reply other threads:[~2014-10-02 14:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2894525.Uqi71VIjsf@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=announce@dpdk.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).