From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tree problem
Date: Thu, 3 May 2007 18:30:19 +0100 [thread overview]
Message-ID: <b8c6c51342c73bbb63ec0d0f766fd6a3@vitanuova.com> (raw)
In-Reply-To: <599f06db0705030925h57ec834dx56a694a2d82f0e1c@mail.gmail.com>
> I want each clunk, not the last one...
there will be at most one clunk for an open
file, as it's illegal to clone an open fid.
in the usual case (when clients are being non-malicious)
destroyfid on an open file will be trigged
by that clunk.
it does seem a pity that there seems to
be no way of delaying the response to a clunk
without stopping the server read loop.
next prev parent reply other threads:[~2007-05-03 17:30 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
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 [this message]
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=b8c6c51342c73bbb63ec0d0f766fd6a3@vitanuova.com \
--to=rog@vitanuova.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).