From: Gerrit Hannaert <degerrit@web.de>
To: Hans Reiser <reiser@namesys.com>, reiserfs-list@namesys.com
Subject: Re: Status of reiserfs in Redhat 2.4.7-10 kernel ?
Date: Wed, 16 Apr 2003 21:55:51 +0200 [thread overview]
Message-ID: <3E9DB547.4030109@web.de> (raw)
In-Reply-To: <3E9D7DA6.8040507@namesys.com>
Hans Reiser wrote:
> Test suites cannot compete with real users. Marcelo gets lots of real
> users before he releases a final version, and the distros don't.
> However, I would also add that a conservative person would wait until
> a few weeks after Marcelo releases, and confirm that it really was
> stable according to those on the linux kernel mailing list.
I think there is something to be said for test suites *and* for testing
by a good number of users, and new kernels should probably get a good
dose of both before running on any production system. You should
probably get as much testing as you can get, and excluding test suites
doesn't sound like a good idea to me - which may not be what Hans meant,
though ;-).
That said, I would really like the vendors' and 'vanilla' kernels to
converge a lot more than they do now... I don't like the idea that some
differences in the source trees have more 'historic' motivations than
being new features or bugfixes (just a hunch). Personally I've been
switching back and forth between vendor and patched 'vanilla' kernels
for the last few years...
- Gerrit
next prev parent reply other threads:[~2003-04-16 19:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 23:10 Status of reiserfs in Redhat 2.4.7-10 kernel ? ahorn
2003-04-15 23:35 ` Philippe Gramoullé
2003-04-16 1:07 ` ahorn
2003-04-16 7:31 ` Oleg Drokin
2003-04-16 7:33 ` Hans Reiser
2003-04-16 8:14 ` ahorn
2003-04-16 16:11 ` Valdis.Kletnieks
2003-04-16 13:17 ` Chris Mason
2003-04-16 15:58 ` Hans Reiser
2003-04-16 19:55 ` Gerrit Hannaert [this message]
2003-04-17 15:57 ` Hans Reiser
2003-04-17 16:18 ` Chris Mason
2003-04-16 7:57 ` Anders Widman
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=3E9DB547.4030109@web.de \
--to=degerrit@web.de \
--cc=reiser@namesys.com \
--cc=reiserfs-list@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.