From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] merge activity report
Date: Mon, 18 May 2009 13:19:46 -0400 [thread overview]
Message-ID: <1242667096-sup-7844@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1242659511-sup-4534@entry>
Excerpts from William Morgan's message of Mon May 18 11:11:58 -0400 2009:
Let me know when you'd like the flexible sent stuff rebased and
against which branch. I'm ready with that any time.
Still working on the locking stuff, which is proving quite
interesting.
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/20090518/59f3b839/attachment.bin>
next prev parent reply other threads:[~2009-05-18 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 15:11 William Morgan
2009-05-18 17:19 ` Ben Walton [this message]
2009-05-18 18:24 ` William Morgan
2009-05-28 15:13 ` William Morgan
2009-05-28 15:31 ` Ben Walton
2009-05-28 16:37 ` 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=1242667096-sup-7844@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