You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make tone more casual and remove overly structured language
- Remove 'Never look like novice again' tagline
- Make README more personal and less structured
- Use casual language based on real experience
- Remove overly formal descriptions
Never send a bad patch again! This toolkit helps you validate patches before sending them to Linux kernel mailing lists.
6
+
Validate patches before sending them to Linux kernel mailing lists.
7
7
8
-
Born from real experience of patch rejections and maintainer feedback, this validator catches the common mistakes that immediately mark you as a novice contributor.
8
+
After getting patches rejected multiple times by maintainers, I built this validator to catch the common mistakes that get patches rejected immediately.
9
9
10
10
## Quick Start
11
11
@@ -176,14 +176,11 @@ Found a bug or have a suggestion? Please contribute!
176
176
177
177
This toolkit is meant to help everyone avoid novice mistakes.
178
178
179
-
## Inspiration
179
+
## Background
180
180
181
-
This validator was created after experiencing real patch rejections from Linux kernel maintainers including:
182
-
- Dan Carpenter's feedback on patch quality
183
-
- Greg KH's automated responses about patch format
184
-
- Multiple v2, v3, v4+ iterations learning the process
181
+
Built this after my patches kept getting rejected for basic formatting issues and style problems. Got tired of the back-and-forth with maintainers like Dan Carpenter and Greg KH over things that should be caught before submitting.
185
182
186
-
Every check in this validator represents a real mistake that was made and learned from.
183
+
Each check here is based on an actual mistake I made and had to fix.
0 commit comments