From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
Stephen Finucane <stephenfinucane@hotmail.com>
Cc: dev@dpdk.org
Subject: Re: DPDK patchwork upgrade
Date: Wed, 07 Sep 2016 19:01:47 +0200 [thread overview]
Message-ID: <9398822.xtO6cvAGR1@xps13> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8973C9D5C64@IRSMSX108.ger.corp.intel.com>
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?
> - Is there any way to see if patches in a patchset have been acked?
> Usually, patchsets are acked by replying to the cover letter,
> but this is not going to be reflected in Patchwork, correct?
Yes, I think the next version of patchwork will support series
and cover letter parsing.
Maybe we could also be able to check the message id of a previous
cover letter before sending a new version of a series?
next prev parent reply other threads:[~2016-09-07 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 15:01 DPDK patchwork upgrade 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 [this message]
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
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=9398822.xtO6cvAGR1@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stephenfinucane@hotmail.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 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.