docs: reporting-issues: a easier process for reporting stable regressions
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest2 patches 2 repliesIn review
Changes in v2 from the cover letter
* inital version, starting straight with v2 to avoid confusion, as one of the patches was submitted earlier already
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | docs: reporting-issues.rst: move tainted check upwardsDocumentation/ | +42 | 0 replies | |
| 2/2 | docs: reporting-issues.rst: shortcut for reporting stable regressionsDocumentation/ | +94 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/2] docs: reporting-issues: a easier process for reporting stable regressions
This series creates a streamlined process for users wanting to report regressions within a stable and longterm kernel series. The existing process is too demanding, complicated and takes too much time for this case.
I didn't CC the stable maintainers here, they need to review the whole document anyway once the last few details have been sorted out.
v2:
* inital version, starting straight with v2 to avoid confusion, as one of the patches was submitted earlier already
Thorsten Leemhuis (2):
docs: reporting-issues.rst: move tainted check upwards
docs: reporting-issues.rst: shortcut for reporting stable regressions
.../admin-guide/reporting-issues.rst | 222 +++++++++++------- 1 file changed, 135 insertions(+), 87 deletions(-)
base-commit: ba5cb300e0b540a330d579402d72cdd1808e5a8f
Signature · 1 line
2.29.2