Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Series parsing confused by reply of a series to a series

Open
#127 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reproducing the reported case from the linked linuxppc-dev thread, where a seven-patch series is followed by a related 25-patch series. Trace the series parsing behavior that produces series 2303, 2306, and 2307; done means the two series are not incorrectly combined and the failure mode is no longer misleading.

Written by the indexing model from the issue text.

Description

bug

For some reason one of our contributors decided to post a series, and then reply to that series with another related series.

https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-September/thread.html#163407

The original series had 7 patches, and the second series had 25.

The result in patchwork is a series of 25, combining the 7 patches form the first series, and then 8-25 from the second series. And then a single patch series for each of the remaining patches in the second series (1-7):

http://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=2303
http://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=2306
http://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=2307

I wouldn't suggest this is necessarily a behaviour patchwork should fully support, but it would be preferable if the failure mode wasn't quite so awkward. ie. Having the two series combined into one is pretty much the worst possible outcome.

Dominant language
Python
Stars
317
Forks
91
PR merge metrics
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.