Have a way to indicate series dependencies
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No files, tests, or entry points are named. Start by locating how cover letters and patch series are parsed and represented, then trace the merge and testing workflow. Done means dependency lines can identify unmerged patch series and those dependencies are considered before merging and testing.
Written by the indexing model from the issue text.
Description
<imre> damien_l: would be nice if we could add "Dependency: <patchset url>" lines to cover letters for unmerged-yet dependencies
This can be used to merge the dependent series before merging the one in question and so be able to properly test it.
- Dominant language
- Python
- Stars
- 22
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 dlespiau/patchwork
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in dlespiau/patchwork
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100