From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] fossil woe
Date: Wed, 7 Dec 2005 16:36:11 -0500 [thread overview]
Message-ID: <ee9e417a0512071336s47c415d9wdb0bba2e3aaefd8@mail.gmail.com> (raw)
In-Reply-To: <775b8d190512071312n1466dae3ke29f2d19ddfc7cc1@mail.gmail.com>
> this misses the point. a cache must cope with an "I'm full"
> condition otherwise it can and will fail. i'd much rather a
> long delay on a file-op when fossil does a "I'm nearly full"
> snap than a few days to rescue a smashed system.
you have the source. please fix it.
russ
next prev parent reply other threads:[~2005-12-07 21:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 21:02 Bruce Ellis
2005-12-06 22:07 ` Russ Cox
2005-12-06 22:19 ` Eric Van Hensbergen
2005-12-06 23:10 ` Bruce Ellis
2005-12-06 23:41 ` Russ Cox
2005-12-06 23:48 ` Bruce Ellis
2005-12-07 21:03 ` rog
2005-12-07 21:07 ` Steve Simon
2005-12-07 21:12 ` Bruce Ellis
2005-12-07 21:36 ` Russ Cox [this message]
2005-12-07 21:55 ` Bruce Ellis
2005-12-07 22:09 ` jmk
2005-12-07 22:41 ` Russ Cox
2005-12-07 21:49 ` jmk
2005-12-07 0:17 ` 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=ee9e417a0512071336s47c415d9wdb0bba2e3aaefd8@mail.gmail.com \
--to=rsc@swtch.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).