From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] merge activity report
Date: Thu, 28 May 2009 11:31:36 -0400 [thread overview]
Message-ID: <1243524514-sup-7560@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1243523591-sup-5117@entry>
Excerpts from William Morgan's message of Thu May 28 11:13:56 -0400 2009:
> Sorry for the delay on this. I've merged down everything related so a
> rebase against master should be pretty easy for you. Once that's done
> I will merge it into next.
No problem. I'd actually rebased against master last night as I'd
seen a flurry of activity on the gitorious rss feed. I did this again
just now and force-pushed my changes to
git://code.chass.utoronto.ca/bwalton-sup.git. [I note this for anyone
that may have pulled from my branch previously...rebasing isn't a nice
thing to do with published branches :) ]
It's the bw/flexible_sent branch available from that URL.
I haven't spent any time on the LockManager stuff in the last week+
though, as the NBA finals have been sapping up my evenings!
Does this rebased branch meet your needs?
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/20090528/d00cca51/attachment.bin>
next prev parent reply other threads:[~2009-05-28 15:31 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
2009-05-18 18:24 ` William Morgan
2009-05-28 15:13 ` William Morgan
2009-05-28 15:31 ` Ben Walton [this message]
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=1243524514-sup-7560@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