From: Hans Reiser <reiser@namesys.com>
To: David Dabbs <david@dabbs.net>
Cc: linux-fsdevel@vger.kernel.org,
'ReiserFS List' <reiserfs-list@namesys.com>,
Peter Foldiak <Peter.Foldiak@st-andrews.ac.uk>
Subject: Re: [RFC] Pathname Semantics with //
Date: Thu, 09 Sep 2004 22:40:03 -0700 [thread overview]
Message-ID: <41413E33.5000501@namesys.com> (raw)
In-Reply-To: <20040910030206.E29B015D9E@mail03.powweb.com>
David Dabbs wrote:
>
>
>
> Do you have a proposal to
>expose metadata on a directory such that it
>
>a) allows one to distinguish a directory entry from directory metadata,
>
>
this should be only a style convention, not a deep semantic difference.
Maybe Peter can comment on this.
>b) uses only already-reserved pathname character(s),
>
>
this is not important in practice
>c) doesn't require any reserved name,
>
>
this is not important in practice
>d) is the same delimiter used for file metadata and
>
>
?
>e) doesn't butt heads with Sus?
>
>
standards are not the future, they are efforts to make the past less
painful.
next prev parent reply other threads:[~2004-09-10 5:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 10:41 [RFC] Pathname Semantics with // David Dabbs
2004-09-08 16:13 ` Hans Reiser
2004-09-09 16:36 ` Peter Foldiak
2004-09-09 19:21 ` David Dabbs
2004-09-10 0:49 ` Hans Reiser
2004-09-10 3:06 ` David Dabbs
2004-09-10 5:40 ` Hans Reiser [this message]
2004-09-09 21:51 ` David Dabbs
2004-09-09 6:10 ` Hans Reiser
2004-09-09 17:33 ` Christian Mayrhuber
2004-09-09 20:17 ` David Dabbs
2004-09-09 20:41 ` Andreas Dilger
2004-09-10 9:11 ` Markus Törnqvist
2004-09-10 10:37 ` Christian Mayrhuber
2004-09-09 23:03 ` Jamie Lokier
2004-09-10 1:37 ` David Dabbs
2004-09-10 9:53 ` [SPAM] " Jamie Lokier
2004-09-10 17:11 ` David Dabbs
2004-09-10 11:47 ` Christian Mayrhuber
2004-09-10 11:06 ` Christian Mayrhuber
-- strict thread matches above, loose matches on Subject: below --
2004-09-10 17:49 David Dabbs
2004-09-09 18:03 ` Hans Reiser
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=41413E33.5000501@namesys.com \
--to=reiser@namesys.com \
--cc=Peter.Foldiak@st-andrews.ac.uk \
--cc=david@dabbs.net \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).