On 31 August 2017 at 02:02, Stephen Finucane wrote:
> On Thu, 2017-08-31 at 09:59 +0100, Stephen Finucane wrote:
>> On Wed, 2017-08-30 at 10:38 -0700, Joe Stringer wrote:
>> > On 29 August 2017 at 02:54, Stephen Finucane wrote:
>
> [snip]
>
>> > However, it seems like this is broken right now. (g
On Thu, 2017-08-31 at 09:59 +0100, Stephen Finucane wrote:
> On Wed, 2017-08-30 at 10:38 -0700, Joe Stringer wrote:
> > On 29 August 2017 at 02:54, Stephen Finucane wrote:
[snip]
> > However, it seems like this is broken right now. (git-pw patch list
> > returns empty list if I have project conf
On Wed, 2017-08-30 at 10:38 -0700, Joe Stringer wrote:
> On 29 August 2017 at 02:54, Stephen Finucane wrote:
> > Now that Patchwork 2.0 is out, folks can start to take advantage of some
> > of the new features that it offers. Chief among these is series support,
> > which is only exposed via the w
On 29 August 2017 at 02:54, Stephen Finucane wrote:
> Now that Patchwork 2.0 is out, folks can start to take advantage of some
> of the new features that it offers. Chief among these is series support,
> which is only exposed via the web UI and new REST API and which, in
> turn, necessitates using
Now that Patchwork 2.0 is out, folks can start to take advantage of some
of the new features that it offers. Chief among these is series support,
which is only exposed via the web UI and new REST API and which, in
turn, necessitates using git-pw rather than pwclient. As such, this tool
is slightly