From: Skip Tavakkolian <skipt@real.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Python filesystem
Date: Thu, 29 Nov 2001 12:02:21 -0800 [thread overview]
Message-ID: <3.0.5.32.20011129120221.01482bf8@mail.real.com> (raw)
In-Reply-To: <200111291928.OAA25251@augusta.math.psu.edu>
In a thread long ago, Rob mentioned an idea proposed by Doug McIlroy for an
indexed/annotated filesystem that would keep an annotation file for each
regular file. It would seem like the right idea for keeping the mod
documentation, etc.
BTW, I've not been able to find any reference to the annotation/fs idea.
Was anything written up (that could be shared)?
>What do we lack then? Locking and management of metadata? There's
>probably a way around those, as well. The revision control FS isn't
>well formed for saving; maybe a better solution would be to echo a
>revision number into a ctl or new file, and then have that create a new
>delta. Write the file into it, and let the FS take care of picking out
>the delta and storing it. Perhaps a metadata file could be associated
>with every file. eg, foo.c;meta, foo.c;1.0, etc.
next prev parent reply other threads:[~2001-11-29 20:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 14:49 Russ Cox
2001-11-29 19:28 ` Dan Cross
2001-11-29 20:02 ` Skip Tavakkolian [this message]
2001-11-29 20:05 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-12-08 19:58 Doug McIlroy
2001-11-30 0:11 geoff
2001-11-30 3:10 ` William Josephson
2001-11-29 23:07 geoff
2001-11-29 23:26 ` George Michaelson
2001-11-29 20:01 Russ Cox
2001-11-29 20:37 ` Dan Cross
2001-11-29 20:49 ` Boyd Roberts
2001-11-30 16:01 ` plan9
2001-12-01 4:44 ` Boyd Roberts
2001-11-29 10:23 rog
2001-11-29 10:54 ` Boyd Roberts
2001-11-28 20:36 David Gordon Hogan
2001-11-28 18:54 Russ Cox
2001-11-28 19:09 ` Matt
2001-11-28 21:46 ` Boyd Roberts
2001-11-29 12:24 ` Matt
2001-11-29 5:49 ` Lucio De Re
2001-11-29 6:30 ` Boyd Roberts
2001-11-29 6:31 ` George Michaelson
2001-11-29 7:10 ` Boyd Roberts
2001-11-29 11:26 ` Sam Holden
2001-12-06 16:56 ` Ralph Corderoy
2001-12-06 17:32 ` Boyd Roberts
2001-11-29 10:50 ` Lucio De Re
2001-11-29 11:06 ` Boyd Roberts
2001-12-06 15:59 ` Ralph Corderoy
2001-11-29 7:21 ` Skip Tavakkolian
2001-11-29 7:32 ` Steve Kilbane
2001-12-03 22:39 ` Laura Creighton
2001-12-07 9:36 ` Ralph Corderoy
2001-12-07 14:07 ` Laura Creighton
2001-11-29 7:37 ` Boyd Roberts
2001-11-29 11:10 ` Christopher Nielsen
2001-11-29 19:51 ` Skip Tavakkolian
2001-11-29 10:08 ` John Murdie
2001-11-29 10:37 ` Boyd Roberts
2001-11-29 12:03 ` Lucio De Re
2001-11-28 18:21 Russ Cox
2001-11-28 18:34 ` Matt
2001-11-28 18:18 Matt
2001-11-30 5:44 ` Quinn Dunkan
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=3.0.5.32.20011129120221.01482bf8@mail.real.com \
--to=skipt@real.com \
--cc=9fans@cse.psu.edu \
/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).