Replacing a single patch in a series to reduce review overhead
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing how Patchwork parses email headers and associates patches with series, then review the linked libc-alpha thread for the replacement case. The change is complete when the standard Supersedes or Obsoletes header can identify a patch replacement and the dependent automatic test framework recognizes the updated series.
Written by the indexing model from the issue text.
Description
It is reasonably common that a small error in a single patch in a long series can be fixed with minimal effort. In that case, resubmitting the series is a huge, unnecessary overhead on reviewers.
For myself, I generally tend to submit such patches with a header like:
[PATCH v5.1 10/12] ...
... as a reply to (In-Reply-To: set to), in this case, [PATCH v5 10/12].
Patchwork does not recognize this pattern, and automatic test framework that depend on it will not operate.
Assuming that recognizing this pattern automagically is not practical, the standard email header "Supersedes:" (alias "Obsoletes:") could be supported to indicate that a patch is intended to replace a previous version in a series.
As one concrete example, see this email thread:
https://inbox.sourceware.org/libc-alpha/20250514221405.471472-13-hpa@zytor.com/
In this case the patch being replaced is 12/12.
- Dominant language
- Python
- Stars
- 317
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getpatchwork/patchwork
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getpatchwork/patchwork#668 ·
-
bug web-ui
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
getpatchwork/patchwork#546 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
getpatchwork/patchwork#664 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
getpatchwork/patchwork#663 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
getpatchwork/patchwork#645 ·
All issues in getpatchwork/patchwork
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openml/openml-python#1749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sipyourdrink-ltd/bernstein#6191 ·