From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] lockmanager
Date: Mon, 15 Jun 2009 13:39:15 -0400 [thread overview]
Message-ID: <1245087383-sup-5205@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1245084879-sup-6794@entry>
Excerpts from William Morgan's message of Mon Jun 15 13:24:08 -0400 2009:
> Sorry for the delay. This looks good. Using a mutex to protect the
> file-locking seems like the right idea. Carry on!
Yah, now that 'stupid Kobe' beat the Magic last night, my evenings
should have more time for completing this. I'm just about finished
integrating it with the mbox code.
I've branched this from bw/flexible_sent, since I thought it made more
sense to go from that than from master w/o the flexible sent
parts...it should still merge decently for you, I think.
The next hurdle will be testing, which I'll need help for, since my
only mbox is sup://sent, which is now legacy only (and at some point
when I'm bored will disappear completely).
Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090615/499ca4b3/attachment.bin>
next prev parent reply other threads:[~2009-06-15 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 0:55 Ben Walton
2009-06-15 17:24 ` William Morgan
2009-06-15 17:39 ` Ben Walton [this message]
2009-06-15 17:50 ` William Morgan
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=1245087383-sup-5205@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/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