From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Uvarov Subject: Re: DPDK patchwork upgrade Date: Tue, 11 Oct 2016 11:42:26 +0300 Message-ID: References: <1736050.3Z5tnqk6B6@xps13> <9398822.xtO6cvAGR1@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Thomas Monjalon , "De Lara Guarch, Pablo" , "dev@dpdk.org" To: Stephen Finucane Return-path: Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) by dpdk.org (Postfix) with ESMTP id 8A0B86CBE for ; Tue, 11 Oct 2016 10:42:27 +0200 (CEST) Received: by mail-oi0-f49.google.com with SMTP id t73so16042918oie.1 for ; Tue, 11 Oct 2016 01:42:27 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 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