From: Hans Reiser <reiser@namesys.com>
To: Matthias Andree <ma+rfs@dt.e-technik.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: I oppose Chris and Jeff's patch to add an unnecessary additional namespace to ReiserFS
Date: Tue, 27 Apr 2004 10:35:39 -0700 [thread overview]
Message-ID: <408E99EB.6050203@namesys.com> (raw)
In-Reply-To: <20040426204037.GA21455@merlin.emma.line.org>
Matthias Andree wrote:
>
>If so, the whole discussion is about getting out of the frying pan and
>into the fire. The traditional approach will then be standards compliant
>but be out-of-band and outside of the file system name space, the new
>approach will be outside of the standards, requiring application
>developers to produce a Linux and a POSIX version.
>
>Or am I barking up the wrong tree?
>
>
>
There is always friction between standards and innovation. One should
comply with standards unless genuinely innovating.
next prev parent reply other threads:[~2004-04-27 17:39 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 [this message]
2004-04-27 18:00 ` Markus Törnqvist
2004-04-26 19:33 ` Christoph Hellwig
2004-04-27 17:29 ` Hans Reiser
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=408E99EB.6050203@namesys.com \
--to=reiser@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ma+rfs@dt.e-technik.uni-dortmund.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox