From: Dave Eckhardt <davide+p9@cs.cmu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil+plan9: disk full revisited
Date: Wed, 22 Nov 2006 21:05:36 -0500 [thread overview]
Message-ID: <24448.1164247536@lunacy.ugrad.cs.cmu.edu> (raw)
In-Reply-To: <871wnw49bk.fsf@jorgito.magma.com.ni>
My whimsical suggestion is that writing a file larger than
fossil's write buffer should be like approaching the event
horizon of a black hole: fossil could deliberately delay
responses to Twrite's (a) generally as space gets low, and
(b) specifically for people extending large files.
Dave Eckhardt
next prev parent reply other threads:[~2006-11-23 2:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 0:24 Georg Lehner
2006-11-22 11:23 ` Robert Raschke
2006-11-23 2:05 ` Dave Eckhardt [this message]
2006-11-29 21:10 ` Georg Lehner
2006-11-29 22:34 ` geoff
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=24448.1164247536@lunacy.ugrad.cs.cmu.edu \
--to=davide+p9@cs.cmu.edu \
--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).