From: Hubert Chan <hubert@uhoreg.ca>
To: reiserfs-list@namesys.com
Subject: Re: More from the Weekday Warriors
Date: Thu, 10 Nov 2005 21:37:41 -0500 [thread overview]
Message-ID: <87hdajrjt6.fsf@evinrude.uhoreg.ca> (raw)
In-Reply-To: <200511092347.32743.pvh@uvic.ca> (Peter van Hardenberg's message of "Wed, 09 Nov 2005 23:47:32 -0800")
On Wed, 09 Nov 2005 23:47:32 -0800, Peter van Hardenberg <pvh@uvic.ca> said:
[...]
> Hans, I like the idea that files should be (for those who want it)
> treatable indistinguishably from directories. The contained-by would
> get very tedious with deep nesting, as that is already how the /
> translates for me.
> I propose this:
> files /are/ a normal directory (for resources) and /have/ an invisible
> subdirectory (for attributes) (perhaps "fivedot"?).
I don't know how hard it would be, but I think it would be best to make
your code as generic as possible, so that it can be changed to make
subfiles accessible as robert/hat-size, robert/...../hat-size, etc.
(I'm not saying that it should be accessible by those names at the same
time, but it should be possible to, say, make a 10-line change in the
code to switch it from one to the other.)
Intuition is great, and I don't want to downplay it, but IMHO sometimes
it may be more revealing to actually try things out and see how it
works.
--
Hubert Chan <hubert@uhoreg.ca> - http://www.uhoreg.ca/
PGP/GnuPG key: 1024D/124B61FA
Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA
Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
next prev parent reply other threads:[~2005-11-11 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 7:47 More from the Weekday Warriors Peter van Hardenberg
2005-11-11 2:37 ` Hubert Chan [this message]
2005-11-11 17:23 ` Lares Moreau
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=87hdajrjt6.fsf@evinrude.uhoreg.ca \
--to=hubert@uhoreg.ca \
--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.