From: David Newall <davidn@davidnewall.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Igor Podlesny <for.poige+linux@gmail.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Hi! I've noticed that kernel.org advertises 2.6.28 as "The latest stable version of the Linux kernel is".
Date: Tue, 30 Dec 2008 00:32:21 +1030 [thread overview]
Message-ID: <4958D86D.2000506@davidnewall.com> (raw)
In-Reply-To: <20081229092124.GA18987@infradead.org>
Christoph Hellwig wrote:
> instead of these rants bug reports would be more useful.
Igor didn't rant, not even a little bit, and it reflects poorly on you
that you engage in hyperbole rather than hear his story. In fact, or at
least in my opinion as a computer programmer with 30 years experience,
he's right: A newly stable kernel is not stable. He might even be right
about regressions since 2.6.24.
It's a sorry day when somebody making a simple, reasonable and accurate
feedback is criticised for not providing bug reports. But don't let him
(or me) stop you guys from toasting your fine success. You believe it's
stable; what more could anyone want?
next prev parent reply other threads:[~2008-12-29 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 5:39 Hi! I've noticed that kernel.org advertises 2.6.28 as "The latest stable version of the Linux kernel is" Igor Podlesny
2008-12-29 6:04 ` Willy Tarreau
2008-12-29 9:21 ` Christoph Hellwig
2008-12-29 10:01 ` Igor Podlesny
2008-12-29 14:02 ` David Newall [this message]
2008-12-29 11:50 ` Éric Piel
2008-12-29 12:51 ` Paul Komkoff
2008-12-29 13:39 ` Igor Podlesny
[not found] <fa.AyhwSGaa29qThLZ5OhBSbACDzmI@ifi.uio.no>
[not found] ` <fa.O2INIKnSvQY5+2WFbCRxoh8xutg@ifi.uio.no>
[not found] ` <fa.fGgFQweuOQlZ5w9soKo4267nPkc@ifi.uio.no>
[not found] ` <4958AF9E.7070005@yahoo.com>
2008-12-29 11:16 ` Igor Podlesny
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=4958D86D.2000506@davidnewall.com \
--to=davidn@davidnewall.com \
--cc=for.poige+linux@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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