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: Chris Mason <mason@suse.com>, Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
	akpm@osdl.org
Subject: Re: I oppose Chris and Jeff's patch to add an unnecessary additional namespace to ReiserFS
Date: Tue, 27 Apr 2004 10:29:19 -0700	[thread overview]
Message-ID: <408E986F.90506@namesys.com> (raw)
In-Reply-To: <20040426203314.A6973@infradead.org>



Christoph Hellwig wrote:

>On Mon, Apr 26, 2004 at 09:59:26AM -0700, Hans Reiser wrote:
>  
>
>>The xattr namespace offers zero functional advantage over the file 
>>namespace.  The use of '.' instead of '/' is idiotic, see the very short 
>>paper "The Hideous Name" by Rob Pike  ( www.cs.bell-labs.com/cm/cs/doc/ 
>>) for why mindlessly varying the separators in hierarchical names 
>>throughout an OS is a bad idea. 
>>    
>>
>
>Hans, where have you been the last three years?  Hiding under a rock?
>
>  
>

>As for ACLs in v3 that's a decision of the maintainer, currently you're
>the formal maintainer, but I don't remember a single patch from you.
>Most of the linux 2.6 work has been done by Chris and quite a bit of
>work by your employees.  Chris is paid for doing a stable and working
>reiserfs variant for SuSE so he seems to be qualified for doing that, to..
>  
>
Did you notice that V4 blows XFS and ReiserFS V3 away in benchmarks?    
That is what I have been doing for 3 years....

See www.namesys.com for details.

  reply	other threads:[~2004-04-27 17:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 19:54 [PATCH] reiserfs v3 patches for 2.6.6-rc2 Chris Mason
2004-04-26 16:59 ` I oppose Chris and Jeff's patch to add an unnecessary additional namespace to ReiserFS Hans Reiser
2004-04-26 17:31   ` Chris Mason
2004-04-26 18:15     ` Hans Reiser
2004-04-26 19:12       ` Mark Hahn
2004-04-26 19:13       ` Chris Mason
2004-04-26 20:40         ` Matthias Andree
2004-04-26 22:20           ` Chris Wright
2004-04-26 23:20           ` Andrew Morton
2004-04-27 17:35           ` Hans Reiser
2004-04-27 18:00       ` Markus   Törnqvist
2004-04-26 19:33   ` Christoph Hellwig
2004-04-27 17:29     ` Hans Reiser [this message]
2004-04-27 17:34       ` Christoph Hellwig
2004-04-27 17:58         ` Hans Reiser
2004-04-27 18:04           ` Christoph Hellwig
2004-04-28  0:10             ` Stefan Traby
2004-04-27 18:07           ` Jeff Garzik
2004-04-28  5:51           ` Meelis Roos
2004-04-30 16:14           ` David Masover
2004-05-02  4:14           ` Rob Landley
2004-04-26 19:56   ` Matt H.

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=408E986F.90506@namesys.com \
    --to=reiser@namesys.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=reiserfs-list@namesys.com \
    --cc=torvalds@osdl.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