From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] skulker
Date: Wed, 16 Jun 2004 12:21:00 -0600 [thread overview]
Message-ID: <c4451fbb99923584f7382c65212d08d7@plan9.ucalgary.ca> (raw)
In-Reply-To: <668c983cf294caedeee7db4ff1bb71da@plan9.escet.urjc.es>
>> t+l -> T (or something else)
>
> Just trying to learn.
> Is there any big deal I'm missing in preserving
> the number of characters?
> We have a place for +a and a place for +l,
> why not just another place for +t ?
I was following the rationale that the first character shows the file
type (DMDIR, DMAPPEND, etc) and the second shows the file mode
(DMEXCL, DMTMP).
while a file cannot be an append-only directory it is entirely
possible for it to be DMEXCL|DMTMP...
maybe packing characters/runes together in bitfield-like fashion
(charfields?) isn't such a good idea after all :)
andrey
next prev parent reply other threads:[~2004-06-16 18:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 10:31 Steve Simon
2004-06-16 11:35 ` Russ Cox
2004-06-16 14:17 ` Fco. J. Ballesteros
2004-06-16 14:40 ` Russ Cox
2004-06-16 14:41 ` C H Forsyth
2004-06-16 15:37 ` andrey mirtchovski
2004-06-16 16:25 ` Fco. J. Ballesteros
2004-06-16 17:36 ` Russ Cox
2004-06-16 17:51 ` rog
2004-06-16 17:49 ` William Josephson
2004-06-16 17:49 ` Fco. J. Ballesteros
2004-06-16 17:59 ` rog
2004-06-16 17:56 ` Fco. J. Ballesteros
2004-06-16 19:21 ` boyd, rounin
2004-06-16 19:41 ` Fco. J. Ballesteros
2004-06-16 20:30 ` boyd, rounin
2004-06-16 20:33 ` Fco. J. Ballesteros
2004-06-16 21:04 ` Christoph Lohmann
2004-06-16 22:07 ` boyd, rounin
2004-06-17 2:58 ` Kenji Okamoto
2004-06-17 3:01 ` Kenji Okamoto
2004-06-17 6:25 ` Kenji Okamoto
2004-06-16 18:21 ` andrey mirtchovski [this message]
2004-06-16 19:18 ` boyd, rounin
2004-06-16 19:34 ` rog
2004-06-16 18:13 ` andrey mirtchovski
2004-06-17 0:21 ` Geoff Collyer
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=c4451fbb99923584f7382c65212d08d7@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).