[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090728195648.GA4833@kroah.com>
Date: Tue, 28 Jul 2009 12:56:48 -0700
From: Greg KH <greg@...ah.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
"Rafael J. Wysocki" <rjw@...k.pl>, Ray Lee <ray-lk@...rabbit.org>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] kdesu broken
On Tue, Jul 28, 2009 at 08:15:53PM +0100, Alan Cox wrote:
>
> > Quite frankly, I don't understand why I should even have to bring these
> > issues up. You should have tried to fix the problem immediately, without
> > arguing against fixing the kernel. Without blaming user space. Without
> > making idiotic excuses for bad kernel behavior.
> >
> > The fact is, breaking regular user applications is simply not acceptable.
> > Trying to blame kernel breakage on the app being "buggy" is not ok. And
> > arguing for almost a week against fixing it - that's just crazy.
>
> I've been working on fixing it. I have spent a huge amount of time
> working on the tty stuff trying to gradually get it sane without breaking
> anything and fixing security holes along the way as they came up. I spent
> the past two evenings working on the tty regressions.
>
> However 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.
Do you have a pointer to your previous queue before you zapped it so
that others might be able to pick it up?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists