Re: Patchwork 2.0 ready for takeoff? (redux)

2017-08-23 Thread Stephen Finucane
On Wed, 2017-08-02 at 11:27 +0100, Stephen Finucane wrote: > On Wed, 2017-07-26 at 17:46 +1000, Andrew Donnellan wrote: > > On 11/07/17 09:10, Daniel Axtens wrote: > > > One last bug: > > > > > > https://lkml.org/lkml/2017/7/8/33 is being incorrectly parsed as > > >

Re: Patchwork 2.0 ready for takeoff? (redux)

2017-08-02 Thread Stephen Finucane
On Wed, 2017-07-26 at 17:46 +1000, Andrew Donnellan wrote: > On 11/07/17 09:10, Daniel Axtens wrote: > > One last bug: > > > > https://lkml.org/lkml/2017/7/8/33 is being incorrectly parsed as > > https://py3.patchwork.dja.id.au/project/netdev/list/?series=4681 > > > > It looks like the square

Re: Patchwork 2.0 ready for takeoff? (redux)

2017-07-26 Thread David Demelier
On Wed, 2017-07-26 at 17:46 +1000, Andrew Donnellan wrote: > How are we going now? I personally have one problem though: https://github.com/getpatchwork/patchwork/issues/111 Regards, -- David ___ Patchwork mailing list Patchwork@lists.ozlabs.org

Re: Patchwork 2.0 ready for takeoff? (redux)

2017-07-26 Thread Andrew Donnellan
On 11/07/17 09:10, Daniel Axtens wrote: One last bug: https://lkml.org/lkml/2017/7/8/33 is being incorrectly parsed as https://py3.patchwork.dja.id.au/project/netdev/list/?series=4681 It looks like the square brackets are confusing the parser some how. After we squash this I say we just ship

Re: Patchwork 2.0 ready for takeoff? (redux)

2017-07-11 Thread Sean Farley
Sean Farley writes: > Daniel Axtens writes: > >> One last bug: >> >> https://lkml.org/lkml/2017/7/8/33 is being incorrectly parsed as >> https://py3.patchwork.dja.id.au/project/netdev/list/?series=4681 >> >> It looks like the square brackets are confusing the

Re: Patchwork 2.0 ready for takeoff? (redux)

2017-07-11 Thread Sean Farley
Daniel Axtens writes: > One last bug: > > https://lkml.org/lkml/2017/7/8/33 is being incorrectly parsed as > https://py3.patchwork.dja.id.au/project/netdev/list/?series=4681 > > It looks like the square brackets are confusing the parser some how. What a coincidence, I have a

Re: Patchwork 2.0 ready for takeoff? (redux)

2017-07-10 Thread Daniel Axtens
One last bug: https://lkml.org/lkml/2017/7/8/33 is being incorrectly parsed as https://py3.patchwork.dja.id.au/project/netdev/list/?series=4681 It looks like the square brackets are confusing the parser some how. After we squash this I say we just ship it. Regards, Daniel Stephen Finucane

Re: Patchwork 2.0 ready for takeoff? (redux)

2017-07-05 Thread Stephen Finucane
On Wed, 2017-07-05 at 09:40 +1000, Daniel Axtens wrote: > Hi, > > > 7364269 parser: > > Support single-patch "series" > > We probably want to see this 'live'. True. fwiw, I parsed the Patchwork archives on a new instance without issue, so base parsing looks to be functioning as expected.

Re: Patchwork 2.0 ready for takeoff? (redux)

2017-07-04 Thread Daniel Axtens
Hi, > 7364269 parser: > Support single-patch "series" We probably want to see this 'live'. > afeaeb2 parser: Use a series even if the version > differs This one I'm also nervous about. I've updated the patchwork.dja family of sites to master, assuming nothing goes wrong in the next couple of

Patchwork 2.0 ready for takeoff? (redux)

2017-07-04 Thread Stephen Finucane
With the last of the fuzz-fix patches merged, I think we're ready to tag either another rc or tag the final release. My personal preference is, of course, to for the latter. I've included a shortlog of the changes below, but tl;dr: they're mostly fuzz fixes along with patches to allow for single