public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "David H. Lynch Jr" <dhlii@comcast.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Reiser4. BEST FILESYSTEM EVER.
Date: Sun, 08 Apr 2007 23:14:49 -0400	[thread overview]
Message-ID: <4619AFA9.8080801@garzik.org> (raw)
In-Reply-To: <4619AA52.5040702@comcast.net>

David H. Lynch Jr wrote:
> Jeff Garzik wrote:
>> If the compelling reason is that it needs a test, I'd say its not ready.
> 
>     Can you please elaborate ? I am not sure I understand what you are
> arguing ?
> 
>     Despite his substantially less than polite rhetoric, I have read
> Hans's post from months if not years ago.
>     Aside from the pissing contests - which where not entirely one
> sided, I actually beleive that Hans made a reasonable case
>     that Reiser4 had gone about as far as it could reasonably go with
> regard to testing, robustness, ... without the broader base of
>     use that even an experimental filesystem in distribution tree would get.
> 
>     I for one would atleast play with it if it were in the distribution
> tree.
>     As far as I could tell pretty much everything else that was demanded
> Hans eventually caved and provided - albeit with much pissing and moaning,
>     and holy than thou rhetoric.
> 
>     The argument that anything that needs testing can't get into the
> distribution tree's is specious. There is alot of poorly tested crap in
> the distribution trees.

I'm arguing against circular logic:  the claim that one cannot determine 
reiser4's true usefulness unless its in the tree.

The better method is to get a distro to add reiser4, _then_ if it proves 
worthy add it to the kernel tree.

Not the other way around.

	Jeff



  reply	other threads:[~2007-04-09  3:14 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46157B5B.5000602@gmail.com>
     [not found] ` <1175817921.18400.1183285196@webmail.messagingengine.com>
     [not found]   ` <461592FB.5060507@zytor.com>
     [not found]     ` <1175819681.20754.1183287946@webmail.messagingengine.com>
     [not found]       ` <461596DE.2020802@zytor.com>
     [not found]         ` <1175823288.25662.1183293506@webmail.messagingengine.com>
     [not found]           ` <4615C780.5040407@zytor.com>
2007-04-06  4:32             ` Reiser4. BEST FILESYSTEM EVER johnrobertbanks
     [not found]               ` <20070406152119.GC4228@delft.aura.cs.cmu.edu>
2007-04-07  2:47                 ` johnrobertbanks
2007-04-07  3:30                   ` Jan Harkes
2007-04-07  5:58                     ` johnrobertbanks
2007-04-07  7:15                       ` Willy Tarreau
2007-04-07 13:47                         ` johnrobertbanks
2007-04-07 14:11                       ` Krzysztof Halasa
2007-04-07 15:07                         ` johnrobertbanks
2007-04-07 16:05                           ` Pekka Enberg
2007-04-07 17:10                         ` Valdis.Kletnieks
2007-04-08 16:31                           ` Adrian Bunk
2007-04-07 17:21                         ` Valdis.Kletnieks
2007-04-08  0:41                           ` Krzysztof Halasa
2007-04-07 17:39                   ` Valdis.Kletnieks
2007-04-08  4:32                     ` David H. Lynch Jr
2007-04-07 19:17               ` Lennart Sorensen
2007-04-08  0:44                 ` johnrobertbanks
2007-04-08  1:27                   ` Lennart Sorensen
2007-04-08  2:56                   ` Theodore Tso
2007-04-08  4:13                     ` johnrobertbanks
2007-04-08 12:48                       ` Jose Celestino
2007-04-08 13:21                         ` johnrobertbanks
2007-04-08 14:14                           ` Willy Tarreau
2007-04-08 17:03                       ` Theodore Tso
2007-04-08 18:18                         ` Jeff Mahoney
2007-04-08  4:32                   ` Christer Weinigel
2007-04-08 21:50                     ` Reiser4. BEST FILESYSTEM EVER - Christer Weinigel johnrobertbanks
2007-04-08 22:58                       ` Richard Knutsson
2007-04-09  5:14                         ` johnrobertbanks
2007-04-09  7:07                           ` Willy Tarreau
2007-04-09 16:10                           ` Richard Knutsson
2007-04-09  1:24                       ` Christer Weinigel
2007-04-09  3:38                         ` David H. Lynch Jr
2007-04-09  3:16                       ` David H. Lynch Jr
2007-04-09  4:25                         ` johnrobertbanks
2007-04-09 18:35                     ` Reiser4. BEST FILESYSTEM EVER Nate Diller
2007-04-08  4:06                 ` David H. Lynch Jr
2007-04-08  9:58                   ` Jeff Garzik
2007-04-09  2:52                     ` David H. Lynch Jr
2007-04-09  3:14                       ` Jeff Garzik [this message]
2007-04-09  4:40                         ` David H. Lynch Jr
2007-04-09  4:58                           ` Jeff Garzik
     [not found]   ` <1175909205.905.1183425104@webmail.messagingengine.com>
2007-04-07  7:45     ` COMPILING AND CONFIGURING A NEW KERNEL johnrobertbanks
2007-04-07 16:57       ` Valdis.Kletnieks
2007-04-08  1:11         ` johnrobertbanks
2007-04-07 12:59 Reiser4. BEST FILESYSTEM EVER Dale Amon
2007-04-07 15:28 ` johnrobertbanks

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=4619AFA9.8080801@garzik.org \
    --to=jeff@garzik.org \
    --cc=dhlii@comcast.net \
    --cc=linux-fsdevel@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