9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil deadlock
Date: Thu, 15 Sep 2011 10:32:22 -0400	[thread overview]
Message-ID: <fe048ff6547499ba1bfdb99e737ab3b3@coraid.com> (raw)
In-Reply-To: <20110915152855.64c7fc6f@kolari.ethans.dre.am>

On Thu Sep 15 10:31:09 EDT 2011, eekee57@fastmail.fm wrote:
> On Thu, 08 Sep 2011 13:48:23 +0100 rod@hemiola.co.uk wrote:
>
> > I can easily get fossil to deadlock.  It would be great if anyone
> > with fossil internals expertise could comment.
> >
> Every now and then someone studies fossil, having the belief that if
> only it were understood it could be made to work properly.  No-one has
> succeeded in gaining "fossil internals expertise" yet, and the
> filesystem is over 10 years old.

i think that's an excellent summary of the issues.

- erik



  reply	other threads:[~2011-09-15 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 12:48 rod
2011-09-15 14:28 ` Ethan Grammatikidis
2011-09-15 14:32   ` erik quanstrom [this message]
2012-03-22 11:57 ` Richard Miller
2012-03-22 13:13   ` Gorka Guardiola
2012-03-22 13:41   ` David du Colombier

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=fe048ff6547499ba1bfdb99e737ab3b3@coraid.com \
    --to=quanstro@labs.coraid.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).