From: "Alexander G. M. Smith" <agmsmith@rogers.com>
To: reiserfs-list@namesys.com
Subject: Re: Carrying Attributes too Far
Date: Thu, 18 Sep 2003 22:52:08 -0400 EDT [thread overview]
Message-ID: <1113133468-BeMail@cr593174-a> (raw)
In-Reply-To: <20030919014548.10229.qmail@web60006.mail.yahoo.com>
Narcoleptic Electron wrote on Thu, 18 Sep 2003 21:45:48 -0400 (EDT):
> Or we could call the attribute directory "@" (XML schemas use this to signify attributes)... however, it could be misconstrued as "at".
>
> "^" looks nice too. It sort of points up toward the containing object, implying a relationship.
>
> It's probably not too important what we call the attribute directory at this point ... is it?
Slightly important. For my RAM file system project, I'm working on an archive format that will store everything (files, directories, links, attributes, indices, volume info, metadata). Kind of like tar :-) Needed so that the RAM disk contents can be optionally saved when it is unmounted. Coincidentally the utilities can work with other file systems. At the moment I have attributes named directly as children of files. For future compatibility, it would be nice to use whatever the attribute directory name is. And standard attribute names for userid and other things. Never mind, getting a standard for that won't happen quickly so I'll just make up my own for now and change it later.
Hans is right, two commas is easier to type. It's also more obvious to the eye than a single comma.
- Alex
next prev parent reply other threads:[~2003-09-19 2:52 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 15:14 Fwd: Re: Reiser4: "pseudo file namespace" suggestion Narcoleptic Electron
2003-09-11 15:18 ` Hans Reiser
2003-09-13 23:59 ` Carrying Attributes too Far (was Reiser4: "pseudo file namespace" suggestion) Alexander G. M. Smith
2003-09-14 1:56 ` Mike Fedyk
2003-09-14 3:46 ` Alexander G. M. Smith
2003-09-14 3:53 ` Carrying Attributes too Far Hubert Chan
2003-09-14 4:21 ` Hubert Chan
2003-09-14 3:39 ` Hubert Chan
2003-09-14 4:21 ` Hubert Chan
2003-09-16 19:15 ` Alexander G. M. Smith
2003-09-18 17:14 ` Narcoleptic Electron
2003-09-18 18:08 ` Hans Reiser
2003-09-18 20:16 ` Alexander G. M. Smith
2003-09-18 20:31 ` Grant Miner
2003-09-18 21:44 ` Alexander G. M. Smith
2003-09-18 22:00 ` Grant Miner
2003-09-18 22:28 ` Narcoleptic Electron
2003-09-18 22:42 ` Hans Reiser
2003-09-18 23:06 ` Grant Miner
2003-09-18 23:17 ` Narcoleptic Electron
2003-09-18 23:23 ` Narcoleptic Electron
2003-09-18 23:28 ` Grant Miner
2003-09-19 0:29 ` Alexander G. M. Smith
2003-09-19 0:28 ` Alexander G. M. Smith
2003-09-19 0:46 ` Hans Reiser
2003-09-19 1:45 ` Narcoleptic Electron
2003-09-19 2:52 ` Alexander G. M. Smith [this message]
2003-09-19 4:40 ` Narcoleptic Electron
2003-09-19 8:42 ` Martin Wilck
2003-09-19 13:27 ` Alexander G. M. Smith
2003-09-19 15:13 ` Martin Wilck
2003-09-19 15:35 ` Alexander G. M. Smith
2003-09-19 15:48 ` Narcoleptic Electron
2003-09-19 13:20 ` Alexander G. M. Smith
2003-09-19 13:46 ` Bennett Todd
2003-09-19 19:31 ` Alexander G. M. Smith
2003-09-19 22:51 ` Narcoleptic Electron
2003-09-20 1:31 ` Hans Reiser
2003-09-22 15:53 ` Attribute Directory Name (Was: Carrying Attributes too Far) Narcoleptic Electron
2003-09-22 20:02 ` Narcoleptic Electron
2003-09-22 22:52 ` Alexander G. M. Smith
2003-09-22 13:28 ` Carrying Attributes too Far lrc1
2003-09-22 22:50 ` Alexander G. M. Smith
2003-09-23 1:21 ` lrc1
2003-09-23 22:48 ` Alexander G. M. Smith
2003-09-24 16:57 ` lrc1
2003-09-24 9:35 ` Hans Reiser
2003-09-24 17:52 ` lrc1
2003-09-24 19:37 ` Hubert Chan
2003-09-25 3:40 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2003-10-04 5:58 lrc1
2003-10-04 18:17 ` Alexander G. M. Smith
2003-10-04 20:10 ` Hubert Chan
2003-12-03 19:18 ` Hans Reiser
2003-12-05 0:30 ` lrc1
2003-12-05 5:27 ` Hubert Chan
2003-12-05 12:38 ` Hans Reiser
2003-12-06 23:33 ` lrc1
2003-12-07 2:48 ` Hubert Chan
2003-12-07 17:08 ` 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=1113133468-BeMail@cr593174-a \
--to=agmsmith@rogers.com \
--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.