sort order lost when updating patches

[Finucane, Stephen]

On 16 May 16:03, Bjorn Helgaas wrote:
> On Sat, May 14, 2016 at 7:21 AM, Len Brown <lenb at kernel.org> wrote:
> > On Wed, May 11, 2016 at 2:36 PM, Bjorn Helgaas <bhelgaas at google.com> wrote:
> >> On Tue, Apr 5, 2016 at 11:27 AM, Bjorn Helgaas <bhelgaas at google.com> wrote:
> >>> 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.

Note to self: add patchwork version to footer.

> >>> 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 can remove
> >>> superceded patches.
> >>> - Mark superceded patches, set "Change state:" to "Superceded", click "update".
> >>> - I'm returned to patches sorted by *date*, not by submitter.
> >>>
> >>> This makes it a real pain to mark superceded patches.

Sorry for not responding to this sooner: seems like there are some
regressions in filtering. If you want to look at it yourself, then
changes to 'filter.py' would be a good place to start. If not, then
I'll have a look into it but it will be a few weeks before I get to do
so (the backlog is huge, plus I've my day job heh).

Stephen