From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] tree problem
Date: Thu, 3 May 2007 08:40:31 -0700 [thread overview]
Message-ID: <13426df10705030840k635ec03fkc5c849dafa46cde8@mail.gmail.com> (raw)
In-Reply-To: <200705031528.l43FSQ006268@zamenhof.cs.utwente.nl>
I'm sort of missing the point here. What was the case where destroyfid
was not sufficient? I don't understand the user reusing a fid if the
user had not stopped using it, i.e. if the user had two references to
the fid, and clunked it once, isn't reusing that fid an error of some
sort?
IIRC destroyfid is just what is called when the ref count is zero,
which is pretty close to what you want much of the time.
(that said, I keep thinking I want clunk in there anyway :)
thanks
ron
next prev parent reply other threads:[~2007-05-03 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 14:22 Gorka Guardiola
2007-05-03 15:01 ` Russ Cox
2007-05-03 15:28 ` Axel Belinfante
2007-05-03 15:40 ` ron minnich [this message]
2007-05-03 15:55 ` Russ Cox
2007-05-03 16:25 ` Gorka Guardiola
2007-05-03 17:22 ` Russ Cox
2007-05-04 7:53 ` Gorka Guardiola
2007-05-03 17:30 ` rog
2007-05-03 20:21 ` Charles Forsyth
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=13426df10705030840k635ec03fkc5c849dafa46cde8@mail.gmail.com \
--to=rminnich@gmail.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).