From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] [PATCH] fossil: fix a deadlock in the caching logic
Date: Tue, 4 Apr 2023 21:50:09 +0100 [thread overview]
Message-ID: <CAOw7k5ib9EN_VmD+6J=+ig-HdD0YDXg5_8pbxMPZZKcPH3uwjg@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5g9xE70VzdSC5hpjs9HVwyhPf=Ao+YN9v32Sb7Ydk9_fg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
One of the nice things about several of the papers at iwp9 was the implied
or express reconsidering of secondary storage given various types of modern
technology.
Fossil works hard to do certain things that now we probably wouldn't bother
to do.
On Tue, 4 Apr 2023 at 21:44, Charles Forsyth <charles.forsyth@gmail.com>
wrote:
> It's funny that usually "it wasn't me" is used when breaking things. here
> it's fixing them, but I'm fairly sure "it wasn't me" that fixed it.
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T354fe702e1e9d5e9-M9c2d5cbd6cdf66a3a9443d64
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1514 bytes --]
next prev parent reply other threads:[~2023-04-04 20:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 17:15 noam
2023-04-04 18:03 ` Steve Simon
2023-04-04 18:34 ` Skip Tavakkolian
2023-04-04 20:44 ` Charles Forsyth
2023-04-04 20:50 ` Charles Forsyth [this message]
2023-04-05 1:59 ` noam
2023-04-05 21:25 ` Charles Forsyth
2023-04-06 3:22 ` noam
2023-04-06 3:57 ` Lucio De Re
2023-04-08 7:50 ` hiro
2023-04-08 14:30 ` Charles Forsyth
2023-04-08 14:36 ` Charles Forsyth
2023-04-08 15:09 ` Dan Cross
2023-04-08 15:27 ` Steffen Nurpmeso
2023-04-08 17:12 ` Bakul Shah
2023-04-04 22:07 ` Anthony Martin
2023-04-05 2:48 ` noam
2023-04-04 22:15 ` noam
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='CAOw7k5ib9EN_VmD+6J=+ig-HdD0YDXg5_8pbxMPZZKcPH3uwjg@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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).