Re: pwclient list issues

On Sat, Oct 12, 2019 at 8:22 AM Stephen Finucane wrote: > > On Thu, 2019-09-19 at 11:49 -0500, Bjorn Helgaas wrote: > > No doubt this is user or installation error, but I haven't a clue. My > > ~/.pwclientrc: > > > > [options] > > default = linux-pci >

Re: [PATCH] Fix issue with delegation of patch via REST API

On Thu, Oct 3, 2019 at 4:22 PM Bjorn Helgaas wrote: > > I can't get patchwork delegation via git-pw to work either on ozlabs > or kernel.org. Any hints on where to look or more data to collect? This magically started working on patchwork.kernel.org. I don't know what changed, but

Re: [PATCH] Fix issue with delegation of patch via REST API

[+cc Daniel, Konstantin] I can't get patchwork delegation via git-pw to work either on ozlabs or kernel.org. Any hints on where to look or more data to collect? Bjorn On Wed, Sep 25, 2019 at 01:51:20PM -0500, Bjorn Helgaas wrote: > On Wed, Sep 25, 2019 at 04:33:35PM +0100, Stephen Finuc

git-pw startup issues

aintainer for project 'Linux PCI development'"]} $ git-pw patch update --delegate bhelg...@google.com 1164343 ... {u'delegate': [u"User 'bhelgaas' is not a maintainer for project 'Linux PCI development'"]} $ git-pw patch update --delegate "Bjorn Helgaas" 1164343 ..

Re: git-pw startup issues

On Sat, Sep 21, 2019 at 1:37 PM Stephen Finucane wrote: > > On Sat, 2019-09-21 at 10:32 -0500, Bjorn Helgaas wrote: > > Hello, > > > > I'm trying to get started with git-pw (or pwclient, but I have the > > impression that's the old stuff, and I don't think it suppo

pwclient list issues

d matching *lorpie01* $ ~/.local/bin/pwclient list -d bhelgaas -s New Patches delegated to Bjorn Helgaas : Traceback (most recent call last): File "/home/bhelgaas/.local/bin/pwclient", line 10, in sys.exit(main()) File "/home/bhelgaas/.local/lib/python2.7/site-p

Re: [PATCH] Fix issue with delegation of patch via REST API

On Wed, Sep 25, 2019 at 04:33:35PM +0100, Stephen Finucane wrote: > On Tue, 2019-09-24 at 14:12 -0500, Bjorn Helgaas wrote: > > On Tue, Sep 24, 2019 at 09:45:16AM +0100, Stephen Finucane wrote: > > > On Mon, 2019-09-23 at 15:39 -0500, Bjorn Helgaas wrote: > > > > On S

Re: [PATCH] Fix issue with delegation of patch via REST API

On Tue, Sep 24, 2019 at 09:45:16AM +0100, Stephen Finucane wrote: > On Mon, 2019-09-23 at 15:39 -0500, Bjorn Helgaas wrote: > > On Sat, Sep 21, 2019 at 07:30:46PM +0100, Stephen Finucane wrote: > > > There have been reports of people being unable to delegate patches to > &g

Re: [PATCH] Fix issue with delegation of patch via REST API

an one delegate found: helgaas Is this another manifestation of the same bug or something else? > [1] > https://github.com/getpatchwork/patchwork/blob/89c924f9bc/patchwork/api/patch.py#L108-L111 > [2] > https://github.com/getpatchwork/patchwork/blob/89c924f9bc/patchwork/models.py#L204-L210

Re: [PATCH] Fix issue with delegation of patch via REST API

[+cc Jeremy, Michael] On Sat, Sep 21, 2019 at 07:30:46PM +0100, Stephen Finucane wrote: > There have been reports of people being unable to delegate patches to > themselves, despite being a maintainer or the project to which the patch > is associated. > > The issue is a result of how we do a

git-pw startup issues

aintainer for project 'Linux PCI development'"]} $ git-pw patch update --delegate bhelg...@google.com 1164343 ... {u'delegate': [u"User 'bhelgaas' is not a maintainer for project 'Linux PCI development'"]} $ git-pw patch update --delegate "Bjorn Helgaas" 1164343 ..

Re: keyboard shortcuts?

On Fri, Jun 8, 2018 at 8:08 AM Stephen Finucane wrote: > > On Wed, 2018-05-23 at 17:46 -0500, Bjorn Helgaas wrote: > > Does patchwork support keyboard shortcuts and I'm just missing them? (I > > see that tab and space do things but I don't see anything else.) Would >

keyboard shortcuts?

Does patchwork support keyboard shortcuts and I'm just missing them? (I see that tab and space do things but I don't see anything else.) Would that be of interest to anybody else? Is anybody already working on it? Bjorn ___ Patchwork mailing list

Re: "Series" support questions

On Fri, Feb 23, 2018 at 8:15 PM, Daniel Axtens wrote: > Hi Bjorn, > >> The new "series" support is seems like a potentially nice thing but >> isn't super useful to me yet. Maybe I'm not using it correctly, or >> maybe there are enhancements planned. Here's what I see: >> >> -

"Series" support questions

The new "series" support is seems like a potentially nice thing but isn't super useful to me yet. Maybe I'm not using it correctly, or maybe there are enhancements planned. Here's what I see: - The "Series" column takes up a lot of horizontal space in the browser window. - The content is

"Submitter" display doesn't decode "encoded-word" syntax

I'm using patchwork 2.0.2.alpha-0 on https://patchwork.ozlabs.org/project/linux-pci/list/ It does not seem to decode the encoded-word [1] syntax used for email headers. For example, the "Submitter" field shows this: =?UTF-8?q?Christian=20K=C3=B6nig?= when it should show this: Christian

linux-pci project not receiving patches?

The linux-pci project (https://patchwork.ozlabs.org/project/linux-pci/list/) doesn't seem to be receiving new emails. The mailing list archive (http://marc.info/?l=linux-pci) shows several new patches that don't appear in patchwork. Did something get broken? Bjorn

Re: sort order lost when updating patches

On Sat, May 14, 2016 at 7:21 AM, Len Brown <l...@kernel.org> wrote: > On Wed, May 11, 2016 at 2:36 PM, Bjorn Helgaas <bhelg...@google.com> wrote: >> On Tue, Apr 5, 2016 at 11:27 AM, Bjorn Helgaas <bhelg...@google.com> wrote: >>> This is on https://patchwork.oz

sort order lost when updating patches

This is on https://patchwork.ozlabs.org/project/linux-pci/list/. I don't see the Patchwork version anywhere, but it's the new stuff. When I update a patch, e.g., to mark it superceded, the patch sort order seems to revert back to date: - Click on "Submitter" heading to sort by submitter so I

Re: [PATCH] Make the submitter name link to a query for that submitter

On Mon, Mar 23, 2015 at 1:56 AM, Michael Ellerman m...@ellerman.id.au wrote: Currently the submitter name is rendered as a mailto: link. This is possibly useful in some circumstances, but in my experience is not usually what I want. Although it opens a mail to the submitter, it doesn't include

ordering by submitter, then date

I use the order-by-submitter view, e.g., http://patchwork.ozlabs.org/project/linux-pci/list/?order=submitter, to weed out superseded patches. This would be easier if I could use two sort keys: first by submitter, then by date. Right now, they are ordered by submitter, but patches from a single