sort order lost when updating patches

Rafael J. Wysocki rafael at kernel.org
Sun May 15 08:14:46 AEST 2016


On Sat, May 14, 2016 at 2:21 PM, 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"?
>
> Rafael relies heavily on patchwork, and "archived"
> and delegation seem to be the key features he uses.


I do.

Delegation is a key feature for me.  I also use different status
flags, but I almost always marked "Superseded" patches as "Archived"
too.

I haven't tried the new stuff yet, thanks for the heads up!


More information about the Patchwork mailing list