Completed
What I will do for you
Class Central Classrooms beta
YouTube playlists curated by Class Central.
Classroom Contents
Best Practices for Getting Your Patches Accepted - Linux Kernel Development
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 69,970 files 29,460,000 lines
- 3 4,659 developers 450+ companies
- 4 10.8 changes per hour
- 5 Top developers by quantity
- 6 Development Process
- 7 "Working upstream saves time and money" Dan Frye - VP Open Systems, IBM Dirk Hohndel - Chief Technologist, Intel
- 8 Patches I received in a 2 week period
- 9 Subject: [PATCH 48/48] ...
- 10 15 patch series, no order given
- 11 Patches 1, 3-10
- 12 "Signed-off-by:" in signature
- 13 Signature saying email was confidential
- 14 Tabs were converted to spaces
- 15 Leading spaces removed
- 16 diff in non-unified format
- 17 Patch created in driver directory
- 18 Made against different tree
- 19 Wrong coding style
- 20 Would not compile
- 21 Broke the build on patch 3/6
- 22 Patches that had nothing to do with me
- 23 1 patch, 450kb big (4500 lines added)
- 24 This was a calm two weeks
- 25 How to do it right
- 26 It is in my self-interest to ignore your patch
- 27 Give me no excuse to reject your patch
- 28 What I will do for you
- 29 Review your patch within 1-2 weeks
- 30 Offer semi-constructive criticism
- 31 Let you know the status of your patch
