From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 45D59ABA for ; Tue, 14 Jul 2015 05:41:44 +0000 (UTC) Received: from ozlabs.org (ozlabs.org [103.22.144.67]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5F9DA32 for ; Tue, 14 Jul 2015 05:41:43 +0000 (UTC) Message-ID: <1436852500.15166.1.camel@ellerman.id.au> From: Michael Ellerman To: Damien Lespiau Date: Tue, 14 Jul 2015 15:41:40 +1000 In-Reply-To: <20150713110536.GA25754@strange.ger.corp.intel.com> References: <201507080121.41463.PeterHuewe@gmx.de> <2102387.OD8sBG4Eol@avalon> <559C73DF.2030008@roeck-us.net> <1436414213.23558.2.camel@ellerman.id.au> <20150713110536.GA25754@strange.ger.corp.intel.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: Jason Cooper , "ksummit-discuss@lists.linuxfoundation.org" , Jeremy Kerr Subject: Re: [Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2015-07-13 at 12:05 +0100, Damien Lespiau wrote: > On Thu, Jul 09, 2015 at 01:56:53PM +1000, Michael Ellerman wrote: > > On Wed, 2015-07-08 at 21:19 +0200, Daniel Vetter wrote: > > > On Wed, Jul 8, 2015 at 4:20 PM, Bjorn Helgaas wrote: > > > > I wish I knew how to use patchwork better, or had a smarter workflow > > > > that could comprehend a series as a single entity. Patchwork is a lot > > > > of clicking, but I don't know anything better. > > > > > > We're working on improving patchwork here to understand series and > > > help out with auto-deprecating patches when new versions show up. > > > Currently being tested internally and we plan to push to upstream ofc > > > and deploy on freedesktop.org (since that's where all the drm/gfx > > > folks hang out), but because of all the things going on it's really > > > slow. Damien knows more, maybe we could push the current state to some > > > git branch somewhere. > > > > I'd be interested in that if you can publish it somewhere. > > > > At the moment I have a very hacky script that tries to recognise a series on > > the client, which usually works, but not always. > > I have quite a few patches on top of upstream now. It's really a back > burner distraction, so well, I have no ETA to give for when I'd be happy > with the state of this work. Yeah fair enough, I'm in the same boat, it's a tool I use for my job but it's not my job to work on the tool :) > I have a work-in-progress branch here: > > https://github.com/dlespiau/patchwork > > What's on there is roughly a re-design of the interface, a new REST API > and parsing/presenting series to the user, not just patches. > > I have some more work (unpublished because not quite ready) on top of > this to parse and present new versions/revisions of series when: > - people post a v2/3/4/... of a patch as a reply to one of the series > - people post a full new series as a v2/3/4/.. > > The goal being one series object (with a unique ID for that patchwork > instance) represents the whole life cycle of that work, including > multiple versions. Sounds great. Maybe we can slowly get some of it merged, I'll try and have a look at it in my copious spare time. cheers