kernelci / kernelci/kci-bisect
Reporting: email and recipient discovery
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Generate a bisection report and work out who to send it to.
Report should include: what regressed, bisection log, suspect commit,
whether the revert verified it.
Recipients: get_maintainers.pl, commit trailers (Signed-off-by etc.),
Lore mbox lookup for the original patch thread.
Start with a fixed moderation list before letting it send to the wild.
There's existing code in kernelci-core/kernelci/bisect.py that does
some of this (get_recipients, get_mbox).
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.
Research direction
Start in kernelci-core/kernelci/bisect.py by reading get_recipients and get_mbox to understand the existing recipient and thread lookup behavior. Define the report around the regression, bisection log, suspect commit, and revert verification, then verify that recipient discovery covers get_maintainers.pl, commit trailers, and the Lore mbox while sending is restricted to a fixed moderation list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100