From: Stephen Finucane <stephenfinucane@hotmail.com>
To: Maxim Uvarov <maxim.uvarov@linaro.org>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK patchwork upgrade
Date: Tue, 11 Oct 2016 09:05:52 +0000 [thread overview]
Message-ID: <DB5PR0301MB21170971D49F3B3866628F25A3DA0@DB5PR0301MB2117.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <CAD8XO3aRe+YsyM7kJqerxAwJAxFYmnrzi9mPKPE_AEvwG3f1_g@mail.gmail.com>
> > You sure can - use the 'retag' command [1]:
> >
> > ./manage.py retag
> >
> > I should probably have included that in the upgrade notes...
> >
> > Stephen
> >
> > [1] https://github.com/getpatchwork/patchwork/blob/stable/1.1/patchwork/management/commands/> retag.py
>
> That is looks really good and should save a lot of time for
> maintainer taking already validated patches. How hard is connection
> between patchwork, mailing list tags and testing system? Is that
> all inside patchwork or you wrote it specially for dpdk? I would
> really like to have the same thing for my projects.
Not difficult at all, and improving all the time. dpdk.org uses upstream
Patchwork, so I'd suggest looking at the documentation [1] for some
advice of getting both developer and deployment versions configured.
Alternatively, Andy Doan in Linaro is working on Patchwork and might be
able to help you out some?
Stephen
[1] patchwork.readthedocs.io/en/latest/development/
prev parent reply other threads:[~2016-10-11 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 15:01 Thomas Monjalon
2016-09-07 15:11 ` Stephen Finucane
2016-09-07 16:40 ` De Lara Guarch, Pablo
2016-09-07 17:01 ` Thomas Monjalon
2016-09-22 6:34 ` Liu, Yong
2016-09-22 8:10 ` Thomas Monjalon
2016-10-10 18:09 ` Stephen Finucane
2016-10-11 8:42 ` Maxim Uvarov
2016-10-11 9:05 ` Stephen Finucane [this message]
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=DB5PR0301MB21170971D49F3B3866628F25A3DA0@DB5PR0301MB2117.eurprd03.prod.outlook.com \
--to=stephenfinucane@hotmail.com \
--cc=dev@dpdk.org \
--cc=maxim.uvarov@linaro.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=thomas.monjalon@6wind.com \
/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).