That screenshot was virtually unreadable. Is he fond of turning his screen contrast up to such eye-searing levels? Or was it just a too-long exposure taken with a hand-held camera?
Andrew "ships" to the other developers. His tree holds the patches from other developers that are likely to make into Linus's tree next. (Linus's tree is the one that is actually released to users. Even then, the code will probably be modified the user's distro.)
The idea is that interested developers can tell how everyone's shiny new patches are going to interact and adjust. I don't know how well it works in practice; IANALKH. (I am not a Linux kernel hacker.) But this is how I understand things to work.
Yikes...
Yikes... Morton scares me. If he doesn't want to fix other people's code, then he should DROP those patches... not ship them.
My eyes!
That screenshot was virtually unreadable. Is he fond of turning his screen contrast up to such eye-searing levels? Or was it just a too-long exposure taken with a hand-held camera?
Keep it back
What? If it's not working it should not be shipped. Drop the patches, don't forward them.
Am I misunderstanding this or is Andrew (hinting at) being reckless?
not as bad as it sounds
Andrew "ships" to the other developers. His tree holds the patches from other developers that are likely to make into Linus's tree next. (Linus's tree is the one that is actually released to users. Even then, the code will probably be modified the user's distro.)
The idea is that interested developers can tell how everyone's shiny new patches are going to interact and adjust. I don't know how well it works in practice; IANALKH. (I am not a Linux kernel hacker.) But this is how I understand things to work.
Sam