The last email from Greg K-H is a gem for many reasons.[1]
"""
And to be a bit more clear about this, having other subsystem
maintainers drop their unwanted code on this subsystem, _without_ even
asking me first is just not very nice. All of a sudden I am now
responsible for this stuff, without me even being asked about it.
Should I start throwing random drivers into the kvm subsystem for them
to maintain because I don't want to? :)
If there's really no other way to do this, than to put it in staging,
let's talk about it. But saying "this must go here" is not a
conversation...
"""
I deeply cherish the fact this stuff is out in public. It helps more junior software devs learn the softer skills.
it was always fun when greg would show up when I was working at the OSDL (he worked across the parking lot from us). always in black pants, a white t-shirt with a pocket (usually holding a pack of cigarettes), and with his hair tied back.
always so humble, and dropping a ton of knowledge and advice. he really is the nice guy that his image projects.
While I did drop by a lot, you aren't describing me, but rather another Linux kernel developer who worked at IBM in our group at the time who is by far more brilliant and smarter than I.
I've never smoked, and at that point in time, I did not have long hair anymore (cut it off when I turned 30 which was before OSDL was ever started.)
> I deeply cherish the fact this stuff is out in public. It helps more junior software devs learn the softer skills.
Agreed, it makes me very happy to see some sanity in open source. In other projects like CPython, expect a little Twitter witch hunt by unproductive project politicians if you object to excessive changes.
Because of CPython's cultural revolution, the hierarchy is:
"""
And to be a bit more clear about this, having other subsystem maintainers drop their unwanted code on this subsystem, _without_ even asking me first is just not very nice. All of a sudden I am now responsible for this stuff, without me even being asked about it. Should I start throwing random drivers into the kvm subsystem for them to maintain because I don't want to? :)
If there's really no other way to do this, than to put it in staging, let's talk about it. But saying "this must go here" is not a conversation...
"""
I deeply cherish the fact this stuff is out in public. It helps more junior software devs learn the softer skills.
[1] https://lwn.net/ml/linux-kernel/YKTsyyVYsHVMQC+G@kroah.com/