From: sinter <sinter.salt@gmx.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG in 2.6.29 final: broken network connection
Date: Tue, 24 Mar 2009 19:18:29 +0100 [thread overview]
Message-ID: <200903241918.29929.sinter.salt@gmx.de> (raw)
In-Reply-To: <20090324172503.1627a3ef@lxorguk.ukuu.org.uk>
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?
next prev parent reply other threads:[~2009-03-24 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 17:12 BUG in 2.6.29 final: broken network connection sinter
2009-03-24 17:25 ` Alan Cox
2009-03-24 17:40 ` Eric Dumazet
2009-03-24 18:18 ` sinter [this message]
2009-03-24 19:42 ` David Miller
2009-03-24 19:42 ` Ingo Molnar
[not found] ` <200903242149.59640.sinter.salt@gmx.de>
2009-03-24 21:45 ` Ingo Molnar
[not found] <cjisi-2Kz-11@gated-at.bofh.it>
[not found] ` <cjiC5-2XR-15@gated-at.bofh.it>
[not found] ` <cjiVm-3mJ-23@gated-at.bofh.it>
2009-03-24 18:40 ` Niel Lambrechts
2009-03-25 12:30 ` markus reichelt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903241918.29929.sinter.salt@gmx.de \
--to=sinter.salt@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox