The Slashdolt writes "After a stern criticism from Linus, the long-time kernel hacker Alan Cox has decided to walk away as the maintainer of the TTY subsystem of the Linux Kernel, stating '...I've had enough. If you think that problem is easy to fix you fix it. Have fun. I've zapped the tty merge queue so anyone with patches for the tty layer
can send them to the new maintainer.'" A response to a subsequent post on the list makes it quite clear that he is serious.
After reading the thread on a mirror, it's important to note that after the argument, Alan and Linus continued to debate the technical merits of how to patch the bugs. The ongoing conversation was civilized and concise. Of course Linus is too much of a pompous ass to apologize to Alan for completely misunderstanding the problem and proposing dangerous and useless ways of fixing it, then arguing about it ad nauseum. Oddly, this doesn't seem to bother Alan or maybe he's just used to it.
I don't personally care what happens to the linux kernel but let me suggest that any of you who depend on a stable USB stack need to take special note of whatever decision Linus finally makes.
How about "Nice work Linus, you'll have the entire kernel back to yourself any day now, I'm sure"
Back three years ago I was sure I'd never leave. Now, I was no kernel dev, but I found out what it was like to try. In the meantime I grew up, and realised there's two sides to Linux.
The 'user' side, where you put up with limited, buggy and badly designed software, finding yourself grateful it even exists, and
The 'dev' side, where your success is proportional to the thickness of your skin. Your willingness to sit there and listen to argue with some other twit whose age you guess at 13 over something you know isn't furthering your project one bit. Oh, and telling people who post "I'm leaving" threads on the forum how wrong they are about everything, and how little their contribution was really worth anyway.
Go and have a look at forums.gentoo.org, where you'll see both at work. I gave up too. For a long time I thought, through contributions and advocacy, I'd help Linux make some real headway in the Server and desktop market. Eventually I came to believe that it would never be big, it'd just mean more communities and more infighting and little real progress.
So I'm sorry, Alan. I'm really sorry, but you've made the right move. Thanks for everything.
Former Gentoo and Debian user here...same experience exactly, except I actually did contribute code from time to time (well, mostly bugfixes). The Gentoo maintainers were particularly rude, and you had to pretty much be rude right back to convince them that what you had done was correct. Totally draining experience.
In an offtopic note, I remember a sort of userland breaking point: I tried to drag and drop a jpg in a browser window (Firefox) to some photo editor. It didn't work. Macs and Windows have been able to do this since at least the mid-90s. I have no idea if you can drag an image from Firefox to the Gimp nowadays, and I don't care.
If Alan Cox wanted to work at Apple, it would take 1 phone call. Devs like him don't have problems getting hired. I don't know if he's been working on FreeBSD or not, but if so that isn't the reason.
Linus is brilliant. He is funny. Most days I really agree with anything he has to say.
However, he has butted heads with people in the past. Perhaps this is just human nature and unavoidable from time to time. Linus isn't perfect, nor always right. I thought he was really unfair to Con Kolivas when he drove Con away.
I've worked with programmers, actors, and people in many other groups where some think they can get away with being a prima donna. I have yet to meet anyone who was in top form in their field that I had to work with who really did have that attitude. I know some are out there, but overall, those that want to do something right are too concerned about what they're doing to pump up their own ego. Generally the best are the ones that know more than others, but because of that, they realize how much they DON'T know and that tends to keep them from getting those ego highs.
Harry Truman used to say he didn't want to talk to experts because an expert was just someone who didn't want to learn anything more on a subject because if he did, then he'd find out he didn't know it all and wasn't an expert any longer.
Harry Truman used to say he didn't want to talk to experts because an expert was just someone who didn't want to learn anything more on a subject because if he did, then he'd find out he didn't know it all and wasn't an expert any longer.
Being smarter is a big factor in programming well. Being obviously smarter than those around you is, well, a major cause of huge ego syndrome.
Don't you get a swollen head when you walk amongst dullards? Every time I see somebody pushing at the 'pull' on a door, I feel my disdain for others rising. When I stand behind a dunce in line, and hear him ask how many eggs in a dozen, I grow more sure of my position among the intellectual greats. When a waiter is unable to figure sums on his pad to give me a total, that I might reimburse him fairly for his service, I scoff at the fools that populate this world. In fact, in every day, in every way, the imbeciles I walk around cause my ego to grow nigh unto titanic proportions, certain I must be nearly akin to God Himself in my intellectual powers.
And I can only program in Basic. Imagine those towers of mind that must be a C programmer!
> I found myself pulling on a door clearly marked Push.
That is actually just an UI bug in the door. If you want people to push a door, you should use a handle that is like a plate, where you can easily put your hand against and push it. If you want people to pull the door open, you need to use vertical rod as a handle, where people can easily grab on to pull it. With this very small change, you don't even need to push/pull texts on the doors.
Also, doors should be always pulled when you go in and pushed when you go out. That makes exiting the building easier in case of emergency (people don't rush to the door and jam it, preventing anyone from pulling it open.) and also when people are trying to get in and out at the same time, the person outside is more capable of keeping the door open for the person going out (it is better that people first get out, before new people get in, because inside there is a limited space, while outside contains usually a lot more room). Also outside usually contains more room for pulling, while the inside often has a wall that limits the space for pulling, especially if you want to keep the door open for someone else.
By his own measure, he says about 2% of the code in today's kernel is written by him, but about 80% of it goes through him before being included. It's unrealistic to expect any one person to have a significant percentage of Linux code literally belong to them, so it would be disingenuous to use that 2% figure as some sort of argument to undermine Linus' authority with regards to the kernel.
Like him or not, Linus is still the man in linux kernel development circles, and for good reason.
Ingo did write the new scheduler, at the request of Linus. Ingo didn't make personal attacks on Con.
Linus was the one for years who said Con was wrong about scheduler theory. Ingo admitted Con was correct, but Linus wouldn't admit he was wrong. Linus asked Ingo to write a new scheduler, basically ignoring the one Con had submitted.
When several people pushed to include Con's scheduler (which at that point was called Staircase) Linus made more personal attacks and wrapped it up saying that Con couldn't be trusted to support his work.
You just need to change in your article the name "linus" by "ingo" and then your post may have some sense. Which shows how much you "know" about the topic.
Linus didn't even bothered with the scheduler, Ingo was the maintainer and it was him who was in charge of deciding what should replace it. It was him who argued, not linus. It was him who ended up admitting that the ideas from Con were good and he wrote the scheduler which is now into the kernel. One that, according to Con, was better than his own scheduler.
Ingo might as well the be the secret lover of Linus or his offspring from a parallel universe. The guy talks so fondly of him you'd think they run through the fields in slow motion towards one another as the Sound of Music is playing in the back drop.
Cox -> submits code which apparently caused a bug User -> Reports breakage Cox -> Can't replicate breakage and asks user for debug info so he can fix it. User -> Says they don't know what to debug for, but is willing to work with Cox. Linus -> Jumps in and calls Cox's code a buggy piece of shit before any debugging took place, and before it is established if the code is buggy or not. Cox -> Continues to troubleshoot the issue. Linus -> Flames Cox personally and says Cox is unwilling to work on the issue. Cox -> Takes his ball and goes home, except in this case, it is OSS so he doesn't really take any ball with him. He just leaves.
The big problem is that there where multiple issues, at least one of which was a userspace bug. Cox originally questioned the Emacs code on one half of the bug, although he seems to have since taken that back. At first Cox seemed insistent on solving the issue one way which appeared to work but was not technically sound. But now he and Linus appear to agree on the basic solution, although a few issues sound like they still need to be hashed out.
I see the tags 'butthurt' and 'whaaaaaaaaa', but no 'thanksforyourtime'. Why won't anyone show any gratitude for the years of work he's generously offered to the project?
I see the tags 'butthurt' and 'whaaaaaaaaa', but no 'thanksforyourtime'. Why won't anyone show any gratitude for the years of work he's generously offered to the project?
If you really want to know, google up the "Greater Internet Fuckwad Theory" and the Penny Arcade comic that comes up will explain it for you, though you can probably guess the gist from the name. Sad but true.
Because the slashdot crowd is composed mostly of whiner douche-bags. The rest of us are masochists so far as I can tell.
After getting my head ripped off for mentioning that I liked operator overloading the other day, I'm trying to figure out why I still post here. I dunno if the crowd is getting nastier or now that I'm far removed from being a teenager, I see how bad it always was. I can't have a reasonable discussion on this site anymore without some asshat hijacking it and turning it into a flame fest.
"Please talk to the new tty maintainer whoever that ends up. I no longer care."
You know what really gets on my nerves? When people say they no longer care, when in reality they do. If he really didn't care, he would have typed the first sentence and stopped.
Linux is a great product, and that is the result of the magnificent work of all the coders and contributers. But sometimes they just act like children.
To be fair, "I no longer care" is shorthand for the closely related "I no longer care enough to put up with the criticism" which is just a statement of cost/benefit analysis. He does care, but not enough to keep going, and that roughly approximates "I don't care".
The argument started when someone found the tty layer had a regression. Linus cares about regression deeply. His basic philosophy is old bug is better than new bug. If a fix introduces a new bug that breaks a real world application, then the fix should be reverted and a better fix should be worked out.
This ensures predictable behavior of an OS that you can actually rely on, and better release management.
Alan didn't think so. He thought his fix was too important to be backed out, although it introduced a regression. Linus was frustrated that he had to explain to Alan, a long time Linux hacker, about the rules. And that's where Alan got impatient too.
Indeed, ive jumped into quite a few projects replacing a previous programmer. Some were experienced and reading their code was really interesting, others were fired for being incompetent and I ended up rewriting most of their code.
In any cases, the first few days, weeks or months depending on the size of the code are spent studying the structure rather than actually coding.
ive jumped into quite a few projects replacing a previous programmer. Some were experienced and reading their code was really interesting, others were fired for being incompetent and I ended up rewriting most of their code.
In any cases, the first few days, weeks or months depending on the size of the code are spent studying the structure rather than actually coding.
The differences here are that A) this is an open-source project, B) this is a *HIGH PROFILE* open source project, and C) Alan was the maintainer, not sole coder (so he both coded, and accepted patches from others.)
It's possible that Alan was the only one who knew anything about the TTY code and how it worked, but I'd doubt it. I'd be really surprised if the new maintainer comes into the role cold.
Are we talking tail-to-nose or is that a phalic reference? OTOH, how you would know your bear's penis length is something that should probably go unsaid.
by Anonymous Coward
on Wednesday July 29, @03:22PM (#28872667)
Yes, indeed it could have been. But unfortunately that's Linus' modus operandi and we all know from long experience that while a great programmer, his ego is far too big to allow him to apologize publicly in the same fashion in which he slammed Alan. Quite unfortunate really since both are quite talented individuals.
You can't expect to publicly berate people and have them bow to your every demand and not have it backfire on you at some point.
Security people are often the black-and-white kind of people that I can't stand. I think the OpenBSD crowd is a bunch of masturbating monkeys, in that they make such a big deal about concentrating on security to the point where they pretty much admit that nothing else matters to them.
First of all I am very greatful for everything he did. I know he contributed a lot. Hope the handover will be more than this emotional message: "Please talk to the new tty maintainer whoever that ends up. I no longer care."
You'll be pleased to hear that not only is Alan helping with the handover, he's been providing some constructive criticism about the way the bug is being fixed now Linus and a few other people have turned their full attention to it.
Thanks (Score:5, Insightful)
Thanks for all the hard work. Good luck to the next maintainer. Not much else to say.
Re:Thanks (Score:5, Insightful)
Parent
Re:Thanks (Score:5, Interesting)
How about "Nice work Linus, you'll have the entire kernel back to yourself any day now, I'm sure"
Back three years ago I was sure I'd never leave. Now, I was no kernel dev, but I found out what it was like to try. In the meantime I grew up, and realised there's two sides to Linux.
Go and have a look at forums.gentoo.org, where you'll see both at work. I gave up too. For a long time I thought, through contributions and advocacy, I'd help Linux make some real headway in the Server and desktop market. Eventually I came to believe that it would never be big, it'd just mean more communities and more infighting and little real progress.
So I'm sorry, Alan. I'm really sorry, but you've made the right move. Thanks for everything.
Parent
Re:Thanks (Score:5, Insightful)
Former Gentoo and Debian user here...same experience exactly, except I actually did contribute code from time to time (well, mostly bugfixes). The Gentoo maintainers were particularly rude, and you had to pretty much be rude right back to convince them that what you had done was correct. Totally draining experience.
In an offtopic note, I remember a sort of userland breaking point: I tried to drag and drop a jpg in a browser window (Firefox) to some photo editor. It didn't work. Macs and Windows have been able to do this since at least the mid-90s. I have no idea if you can drag an image from Firefox to the Gimp nowadays, and I don't care.
Parent
Re:So long and thanks for all the code. (Score:5, Insightful)
If Alan Cox wanted to work at Apple, it would take 1 phone call. Devs like him don't have problems getting hired. I don't know if he's been working on FreeBSD or not, but if so that isn't the reason.
Parent
Linus (Score:5, Interesting)
Linus is brilliant. He is funny. Most days I really agree with anything he has to say.
However, he has butted heads with people in the past. Perhaps this is just human nature and unavoidable from time to time. Linus isn't perfect, nor always right. I thought he was really unfair to Con Kolivas when he drove Con away.
Re:Linus (Score:5, Insightful)
I'm tired of that silly myth.
The best programmers I have met were nice people and they were very easy to get along with and work with.
Parent
Re:Linus (Score:5, Insightful)
You forgot to use the word "inversely" in that statement.
Parent
Re:Linus (Score:5, Insightful)
I've worked with programmers, actors, and people in many other groups where some think they can get away with being a prima donna. I have yet to meet anyone who was in top form in their field that I had to work with who really did have that attitude. I know some are out there, but overall, those that want to do something right are too concerned about what they're doing to pump up their own ego. Generally the best are the ones that know more than others, but because of that, they realize how much they DON'T know and that tends to keep them from getting those ego highs.
Parent
Re:Linus (Score:5, Informative)
That's called the Dunning-Kruger effect [wikipedia.org]
Parent
Re:Linus (Score:5, Interesting)
Harry Truman used to say he didn't want to talk to experts because an expert was just someone who didn't want to learn anything more on a subject because if he did, then he'd find out he didn't know it all and wasn't an expert any longer.
Parent
Re:Linus (Score:5, Funny)
Harry Truman used to say he didn't want to talk to experts because an expert was just someone who didn't want to learn anything more on a subject because if he did, then he'd find out he didn't know it all and wasn't an expert any longer.
Yeah, Harry was a real expert on experts.
Parent
Re:Linus (Score:5, Insightful)
Bullshit. The best programmers don't know if they're awesome. They just think everyone else is stupid.
Parent
Re:Linus (Score:5, Funny)
Being smarter is a big factor in programming well. Being obviously smarter than those around you is, well, a major cause of huge ego syndrome.
Don't you get a swollen head when you walk amongst dullards? Every time I see somebody pushing at the 'pull' on a door, I feel my disdain for others rising. When I stand behind a dunce in line, and hear him ask how many eggs in a dozen, I grow more sure of my position among the intellectual greats. When a waiter is unable to figure sums on his pad to give me a total, that I might reimburse him fairly for his service, I scoff at the fools that populate this world. In fact, in every day, in every way, the imbeciles I walk around cause my ego to grow nigh unto titanic proportions, certain I must be nearly akin to God Himself in my intellectual powers.
And I can only program in Basic. Imagine those towers of mind that must be a C programmer!
Parent
Re:Linus (Score:5, Interesting)
That is actually just an UI bug in the door. If you want people to push a door, you should use a handle that is like a plate, where you can easily put your hand against and push it. If you want people to pull the door open, you need to use vertical rod as a handle, where people can easily grab on to pull it. With this very small change, you don't even need to push/pull texts on the doors.
Also, doors should be always pulled when you go in and pushed when you go out. That makes exiting the building easier in case of emergency (people don't rush to the door and jam it, preventing anyone from pulling it open.) and also when people are trying to get in and out at the same time, the person outside is more capable of keeping the door open for the person going out (it is better that people first get out, before new people get in, because inside there is a limited space, while outside contains usually a lot more room). Also outside usually contains more room for pulling, while the inside often has a wall that limits the space for pulling, especially if you want to keep the door open for someone else.
Parent
Re:Linus (Score:5, Interesting)
The quality of a programmer is often proportional to his ego.
Be careful: Humans confuse cockiness with expertise [newscientist.com].
Parent
Re:Linus (Score:5, Interesting)
Serious question: what percentage of the current Linux kernel was actually written by Linus?
Parent
Re:Linus (Score:5, Informative)
Like him or not, Linus is still the man in linux kernel development circles, and for good reason.
Parent
Re:Linus (Score:5, Interesting)
I read the LKML for years.
Ingo did write the new scheduler, at the request of Linus. Ingo didn't make personal attacks on Con.
Linus was the one for years who said Con was wrong about scheduler theory. Ingo admitted Con was correct, but Linus wouldn't admit he was wrong. Linus asked Ingo to write a new scheduler, basically ignoring the one Con had submitted.
When several people pushed to include Con's scheduler (which at that point was called Staircase) Linus made more personal attacks and wrapped it up saying that Con couldn't be trusted to support his work.
Ingo had nothing to do with that.
Parent
Re:Linus (Score:5, Funny)
You just need to change in your article the name "linus" by "ingo" and then your post may have some sense. Which shows how much you "know" about the topic.
Linus didn't even bothered with the scheduler, Ingo was the maintainer and it was him who was in charge of deciding what should replace it. It was him who argued, not linus. It was him who ended up admitting that the ideas from Con were good and he wrote the scheduler which is now into the kernel. One that, according to Con, was better than his own scheduler.
Ingo might as well the be the secret lover of Linus or his offspring from a parallel universe. The guy talks so fondly of him you'd think they run through the fields in slow motion towards one another as the Sound of Music is playing in the back drop.
Parent
Re:Linus (Score:5, Interesting)
I'm reading the thread. This is my take.
Cox -> submits code which apparently caused a bug
User -> Reports breakage
Cox -> Can't replicate breakage and asks user for debug info so he can fix it.
User -> Says they don't know what to debug for, but is willing to work with Cox.
Linus -> Jumps in and calls Cox's code a buggy piece of shit before any debugging took place, and before it is established if the code is buggy or not.
Cox -> Continues to troubleshoot the issue.
Linus -> Flames Cox personally and says Cox is unwilling to work on the issue.
Cox -> Takes his ball and goes home, except in this case, it is OSS so he doesn't really take any ball with him. He just leaves.
Parent
Re:Linus (Score:5, Informative)
The whole thing is publicly available. See This Google Groups thread [google.com]
The big problem is that there where multiple issues, at least one of which was a userspace bug. Cox originally questioned the Emacs code on one half of the bug, although he seems to have since taken that back. At first Cox seemed insistent on solving the issue one way which appeared to work but was not technically sound. But now he and Linus appear to agree on the basic solution, although a few issues sound like they still need to be hashed out.
Overall a classic miscommunication flare-up.
Parent
No gratitude? (Score:5, Insightful)
Re:No gratitude? (Score:5, Funny)
Parent
Re:No gratitude? (Score:5, Informative)
I see the tags 'butthurt' and 'whaaaaaaaaa', but no 'thanksforyourtime'. Why won't anyone show any gratitude for the years of work he's generously offered to the project?
If you really want to know, google up the "Greater Internet Fuckwad Theory" and the Penny Arcade comic that comes up will explain it for you, though you can probably guess the gist from the name. Sad but true.
Parent
Re:No gratitude? (Score:5, Insightful)
Because the slashdot crowd is composed mostly of whiner douche-bags. The rest of us are masochists so far as I can tell.
After getting my head ripped off for mentioning that I liked operator overloading the other day, I'm trying to figure out why I still post here. I dunno if the crowd is getting nastier or now that I'm far removed from being a teenager, I see how bad it always was. I can't have a reasonable discussion on this site anymore without some asshat hijacking it and turning it into a flame fest.
Parent
Re:No gratitude? (Score:5, Insightful)
Ha. Yes. You did indeed fix that for me.
(And I got modded insightful for my own whining? WTF?)
Parent
On slashdotting... (Score:5, Interesting)
WHY can't lkml.org's mailing list retriever handle a slashdotting?
Its not like the flashcrowds are all THAT big.
Re:On slashdotting... (Score:5, Informative)
Try Google Groups [google.com].
That's the entire thread, supposedly.
Parent
Slashdotted - Google Cache. (Score:5, Informative)
In before the Karma-Whores.
"stern criticism" -> http://74.125.155.132/search?q=cache:http://lkml.org/lkml/2009/7/28/373&hl=en&strip=1
"decided to walk away" -> http://74.125.155.132/search?q=cache:http://lkml.org/lkml/2009/7/28/375&hl=en&strip=1
"quite clear that he is serious" -> http://74.125.155.132/search?q=cache:http://lkml.org/lkml/2009/7/28/378&hl=en&strip=1
Re:Slashdotted - Google Cache the real links (Score:5, Insightful)
care."
You know what really gets on my nerves? When people say they no longer care, when in reality they do. If he really didn't care, he would have typed the first sentence and stopped.
Linux is a great product, and that is the result of the magnificent work of all the coders and contributers. But sometimes they just act like children.
Parent
Re:Slashdotted - Google Cache the real links (Score:5, Insightful)
Parent
*It happens (Score:5, Informative)
Time for all to give Alan a sound round of applause and thanks! The TTY subsystem is a gem thanks to his work.
In other News . . (Score:5, Funny)
Alan Cox announces he will maintain Slashcode: "After this, it will be bloody easy to maintain the Slashcode codebase."
Could anyone shed some light... (Score:5, Interesting)
Thank You (Score:5, Insightful)
Handbags at 10 paces... (Score:5, Funny)
"You claim that emacs sh*ts itself when it gets EAGAIN, and you think
that's an emacs bug. And I think you're full of crap..."
I'm sure there's a job waiting in the diplomatic corps for Mr Torvalds...
I knew it (Score:5, Funny)
probably went like this (Score:5, Funny)
Alan: No Way! i quit!
Linus was right (Score:5, Insightful)
As always.
The argument started when someone found the tty layer had a regression. Linus cares about regression deeply. His basic philosophy is old bug is better than new bug. If a fix introduces a new bug that breaks a real world application, then the fix should be reverted and a better fix should be worked out.
This ensures predictable behavior of an OS that you can actually rely on, and better release management.
Alan didn't think so. He thought his fix was too important to be backed out, although it introduced a regression. Linus was frustrated that he had to explain to Alan, a long time Linux hacker, about the rules. And that's where Alan got impatient too.
Re:Interesting... (Score:5, Interesting)
Indeed, ive jumped into quite a few projects replacing a previous programmer. Some were experienced and reading their code was really interesting, others were fired for being incompetent and I ended up rewriting most of their code.
In any cases, the first few days, weeks or months depending on the size of the code are spent studying the structure rather than actually coding.
Parent
Re:Interesting... (Score:5, Interesting)
ive jumped into quite a few projects replacing a previous programmer. Some were experienced and reading their code was really interesting, others were fired for being incompetent and I ended up rewriting most of their code.
In any cases, the first few days, weeks or months depending on the size of the code are spent studying the structure rather than actually coding.
The differences here are that A) this is an open-source project, B) this is a *HIGH PROFILE* open source project, and C) Alan was the maintainer, not sole coder (so he both coded, and accepted patches from others.)
It's possible that Alan was the only one who knew anything about the TTY code and how it worked, but I'd doubt it. I'd be really surprised if the new maintainer comes into the role cold.
Parent
Requisite XKCD answers your question (Score:5, Funny)
http://xkcd.com/323/ [xkcd.com]
Parent
Re:Interesting... (Score:5, Funny)
Parent
Re:Should I? (Score:5, Funny)
How long does a bear have to be? Is it proportional to long cat?
Parent
Re:Should I? (Score:5, Funny)
Parent
Re:Open-Source developers are jerks (Score:5, Insightful)
The overwhelming majority of people I have encountered are jerks. That's nothing open source developers, or any kind of developer, has a monopoly on.
Parent
Rarely the diplomate (Score:5, Insightful)
Yes, indeed it could have been. But unfortunately that's Linus' modus operandi and we all know from long experience that while a great programmer, his ego is far too big to allow him to apologize publicly in the same fashion in which he slammed Alan. Quite unfortunate really since both are quite talented individuals.
You can't expect to publicly berate people and have them bow to your every demand and not have it backfire on you at some point.
Parent
Re:Rarely the diplomate (Score:5, Funny)
Yes, he can be pretty abrasive. Consider this: http://thread.gmane.org/gmane.linux.kernel/701694/focus=706950 [gmane.org]
Security people are often the black-and-white kind of people that I can't
stand. I think the OpenBSD crowd is a bunch of masturbating monkeys, in
that they make such a big deal about concentrating on security to the
point where they pretty much admit that nothing else matters to them.
(emphasis mine)
Parent
Re:Not very responsible either (Score:5, Informative)
First of all I am very greatful for everything he did. I know he contributed a lot. Hope the handover will be more than this emotional message: "Please talk to the new tty maintainer whoever that ends up. I no longer care."
You'll be pleased to hear that not only is Alan helping with the handover, he's been providing some constructive criticism about the way the bug is being fixed now Linus and a few other people have turned their full attention to it.
Parent