From: Maxim Uvarov <maxim.uvarov@linaro.org>
To: Stephen Finucane <stephenfinucane@hotmail.com>
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 11:42:26 +0300 [thread overview]
Message-ID: <CAD8XO3aRe+YsyM7kJqerxAwJAxFYmnrzi9mPKPE_AEvwG3f1_g@mail.gmail.com> (raw)
In-Reply-To: <DB5PR0301MB2117F19266B6189D35E97756A3DB0@DB5PR0301MB2117.eurprd03.prod.outlook.com>
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.
Thank you,
Maxim.
On 10 October 2016 at 21:09, Stephen Finucane <stephenfinucane@hotmail.com>
wrote:
> > 2016-09-07 16:40, De Lara Guarch, Pablo:
> > > I am looking at it, and I see two issues:
> > > - There are some patches that have been acked, but I don't see that in
> patchwork
> > > (e.g. http://dpdk.org/dev/patchwork/patch/15381/)
> >
> > Yes the new columns are empty.
> > I guess they will be filled starting from now.
> > Stephen, could we re-parse old emails (from August/September) to fill
> > A/R/T without breaking the database?
>
> 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
next prev parent reply other threads:[~2016-10-11 8:42 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 [this message]
2016-10-11 9:05 ` Stephen Finucane
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=CAD8XO3aRe+YsyM7kJqerxAwJAxFYmnrzi9mPKPE_AEvwG3f1_g@mail.gmail.com \
--to=maxim.uvarov@linaro.org \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stephenfinucane@hotmail.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).