Patches ordered by arrival time, rather than patch number

Open
#386 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api, frontend

Research direction

Start by reproducing the ordering in the UI and JSON API with the example series at https://patchwork.kernel.org/api/series/390649/. Compare the current arrival-time order with the expected patch-number order, and verify that both interfaces list patches sequentially so clients can apply and bisect them individually.

Written by the indexing model from the issue text.

Description

enhancement

Both UI and JSON API orders patches by date, rather that patch number in the series, so clients can't apply patches one by one.

mbox of the entire series is correct, but for build bots is useful to apply each patch individually and build test to check for patches which may break bisection.

See this series as an example: https://patchwork.kernel.org/api/series/390649/
First patch listed is patch 10/10, because it arrived first.

Dominant language
Python
Stars
317
Forks
91
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getpatchwork/patchwork

All issues in getpatchwork/patchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.