On Wed, 2017-09-20 at 14:04 +0300, Stijn Tintel wrote: > On 20-09-17 13:27, Stephen Finucane wrote: > > On Mon, 2017-09-18 at 16:10 +0800, Jeremy Kerr wrote: > > > Hi Stijn, > > > > > > > I am trying to use git-pw, which uses the new API in patchwork 2.0, but > > > > as soon as add a project to the filter, the list of patches is empty. > > > > Any idea what might be wrong here? > > > > https://patchwork.ozlabs.org/api/patches/ vs > > > > https://patchwork.ozlabs.org/api/patches/?project=lede&submitter=&deleg > > > > ate= > > > > &state=&archived=1&before=&since= > > > > > > I'm no expert on the API (I wasn't involved in writing it), but it looks > > > like you need to reference the project by id, not shortname: > > > > Not quite. We support filtering by both ID and project name, however, there > > was > > a bug in 2.0 [1] that broke the latter. The patch [2] has been backported > > to > > 'stable/2.0' [3] and should probably be cherry-picked into whatever branch > > ozlabs.org is using. > > Thanks for the replies guys, I switched to ID for now and this works > fine. Already merged my first series with git-pw.
Good to hear. Do let me know if you have any questions/comments on the tool: I've been using it for months now without issue but everyone works differently :) > @Jeremy: can you let me know when the patch is in, so I can retest with > project name? Stephen _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork