From: sinter <sinter.salt@gmx.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: BUG in 2.6.29 final: broken network connection
Date: Tue, 24 Mar 2009 19:18:29 +0100
User-Agent: KMail/1.11.1 (Linux/2.6.29; KDE/4.2.1; i686; ; )
References: <200903241812.14577.sinter.salt@gmx.de> <20090324172503.1627a3ef@lxorguk.ukuu.org.uk>
In-Reply-To: <20090324172503.1627a3ef@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Message-Id: <200903241918.29929.sinter.salt@gmx.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 772
Lines: 18

Am Dienstag 24 M?rz 2009 18:25:03 schrieben Sie:
> > It cost me almost 1 complete day
>
> Wouldn't it have been simpler to wait when you found a problem and read
> Ingo's email on the subject from a few hours ago ?

Wouldn't it be simpler to restrictively avoid crap code in final kernel 
versions? And if that does not work by appeal shouldn't the netdev maintainer 
simply be substituted?

Who needs a maintainer adding his SOB with closed eyes under untested crap 
code? Who needs someone like that for kernel development?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/