From: mjt@nysv.org
To: David Masover <ninja@slaphack.com>
Cc: Valdis.Kletnieks@vt.edu, Pysiak Satriani <pysiak.satriani@wp.pl>,
reiserfs-list@namesys.com
Subject: Re: Reiser4 O_DIRECT
Date: Mon, 23 May 2005 12:52:12 +0300 [thread overview]
Message-ID: <20050523095212.GD11013@nysv.org> (raw)
In-Reply-To: <4291225B.5090503@slaphack.com>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On Sun, May 22, 2005 at 07:22:51PM -0500, David Masover wrote:
>
>This is exactly why it should be in the kernel once the developers can't
>find any more bugs. Marked as experimental, mainly, but in the kernel
>where real users can throw cobol/Java/sql bastardizations at it and
>break it.
Sure.
Don't get me wrong on this, because I've voiced my opinion about
the new development model failing us, with stuff getting a bit
too lively in -mm and merged into stable a bit too fast for comfort.
Still, this new model would allow someone to merge Reiser4 into
vanilla with ease, whereas on the traditional model, kicking
an experimental fs from the dev tree might have been a difficult
political move.
Thus it must be anounced in a way that doesn't scare people away
"oh no this is yet another broken pile from -mm, we don't want it!"
but invite them "kickass, a file system that's stable enough to
be merged, with EXPERIMENTAL just pro forma on it"
>Of course, I've worked on sufficiently few big projects that I'm still
>naive enough to believe that unit tests _can_ catch everything, if
>they're done right. I'm sure I'll eventually be proven wrong...
My take on testing is that I leave it to the real professionals and
with cases like Reiser4, I just blindly do what I'm told and see if
I break anything.
I'm sure a testing professional will happily prove you wrong ;)
--
mjt
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-23 9:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 17:53 Reiser4 O_DIRECT Martin Piayda
2005-05-20 8:42 ` Vladimir Saveliev
2005-05-21 21:49 ` Re[2]: " Pysiak Satriani
2005-05-22 7:43 ` Hans Reiser
2005-05-22 17:12 ` mjt
2005-05-22 17:31 ` Hans Reiser
2005-05-22 17:38 ` Martin Piayda
2005-05-26 19:25 ` evilninja
2005-05-22 22:47 ` Re[2]: " Valdis.Kletnieks
2005-05-23 0:22 ` David Masover
2005-05-23 1:04 ` Valdis.Kletnieks
2005-05-23 9:52 ` mjt [this message]
2005-05-23 16:53 ` Valdis.Kletnieks
2005-05-23 17:53 ` Hans Reiser
2005-05-24 21:35 ` David Masover
2005-05-24 21:55 ` Valdis.Kletnieks
2005-05-24 23:28 ` David Masover
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=20050523095212.GD11013@nysv.org \
--to=mjt@nysv.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=ninja@slaphack.com \
--cc=pysiak.satriani@wp.pl \
--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.