From: Christoph Hellwig <hch@infradead.org>
To: Hans Reiser <reiser@namesys.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Jones <davej@redhat.com>,
jmerkey@comcast.net, Pete Harlan <harlan@artselect.com>,
linux-kernel@vger.kernel.org
Subject: Re: Ext3 File System "Too many files" with snort
Date: Sat, 10 Jul 2004 19:54:03 +0100 [thread overview]
Message-ID: <20040710185403.GA19329@infradead.org> (raw)
In-Reply-To: <40F02E05.8090401@namesys.com>
On Sat, Jul 10, 2004 at 10:57:25AM -0700, Hans Reiser wrote:
> RHEL applies all sorts of patches that have not been tested in mainline,
> and then tells its customers that it is more stable when the reverse is
> true. RHEL should pick a stable mainline kernel 6 weeks after it has
> proven stable, and use it.
I haven't heard that big complains about RH stability yet, but applying
random vendor patches increases Q&A costs - apparently RH seems to be quite
successfull with that business model anyway.
> Their not applying reiserfs bugfixes that are present in the mainline is
> just more evidence that they don't care about stability as much as
> marketing.
Why the heck should they waste ressources with backporting reiserfs fixes
if they don't support it? If you care for reiserfs stability in RHEL send
them patches, that's what SGI did for XFS in Fedora Core 2.
next prev parent reply other threads:[~2004-07-10 18:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 19:20 Ext3 File System "Too many files" with snort jmerkey
2004-07-10 5:07 ` Hans Reiser
2004-07-10 8:33 ` Dave Jones
2004-07-10 17:37 ` Hans Reiser
2004-07-10 17:44 ` Christoph Hellwig
2004-07-10 17:57 ` Hans Reiser
2004-07-10 18:54 ` Christoph Hellwig [this message]
2004-07-10 19:23 ` Hans Reiser
2004-07-12 10:20 ` Paolo Ciarrocchi
2004-07-12 12:11 ` Jesper Juhl
2004-07-12 23:05 ` Bernd Eckenfels
2004-07-18 7:22 ` Hans Reiser
2004-07-10 19:11 ` Francois Romieu
-- strict thread matches above, loose matches on Subject: below --
2004-07-10 6:00 jmerkey
2004-07-10 8:38 ` Dave Jones
2004-07-09 23:11 jmerkey
2004-07-09 19:01 jmerkey
2004-07-09 19:08 ` Pete Harlan
2004-07-14 3:37 ` Ben Hoskings
2004-07-09 18:51 jmerkey
2004-07-09 18:30 jmerkey
2004-07-09 18:44 ` Hans Reiser
2004-07-09 22:26 ` Andreas Dilger
2004-07-09 18:30 jmerkey
2004-07-09 16:36 jmerkey
2004-07-09 17:04 ` Dave Jones
2004-07-08 17:51 jmerkey
2004-07-08 18:21 ` Andreas Dilger
2004-07-11 14:55 ` Michelle Konzack
2004-07-11 17:16 ` Andreas Dilger
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=20040710185403.GA19329@infradead.org \
--to=hch@infradead.org \
--cc=davej@redhat.com \
--cc=harlan@artselect.com \
--cc=jmerkey@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.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