public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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 10:57:25 -0700	[thread overview]
Message-ID: <40F02E05.8090401@namesys.com> (raw)
In-Reply-To: <20040710174432.GA18719@infradead.org>

Christoph Hellwig wrote:

>On Sat, Jul 10, 2004 at 10:37:39AM -0700, Hans Reiser wrote:
>  
>
>>Fedora is something new.  It is good that fedora tracks the mainline.  
>>Kudos for that.  You should do that with RHEL.
>>    
>>
>
>Does someone volunteer to sponsor Hans a free "Release Managment 101" course?
>
>
>  
>
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.
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.

Lindows does it right.

Hans

  reply	other threads:[~2004-07-10 17:57 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 [this message]
2004-07-10 18:54           ` Christoph Hellwig
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=40F02E05.8090401@namesys.com \
    --to=reiser@namesys.com \
    --cc=davej@redhat.com \
    --cc=harlan@artselect.com \
    --cc=hch@infradead.org \
    --cc=jmerkey@comcast.net \
    --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