sort order lost when updating patches
bhelgaas at google.com
Tue May 17 07:03:49 AEST 2016
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.
>>> 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.
> Does it help to mark the superceded patch as "archived"?
Nope, it doesn't make any difference if I mark superceded patches as
"archived" as well as "superceded".
The problem is that when I click the "update" button and the page
reloads, it reverts to the default "sorted by date" order.
More information about the Patchwork