Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] [PATCH] Unbreak "bounce-command" hook (was referencing an nonexistent variable)
Date: Mon, 27 Jul 2009 12:30:20 -0400	[thread overview]
Message-ID: <1248712092-sup-5843@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1248711899-sup-4693@ntdws12.chass.utoronto.ca>

Excerpts from Ben Walton's message of Mon Jul 27 12:25:52 -0400 2009:
> Sorry.  I didn't publish the change, I thought it would be `git am`'d
> from the original mail.  I applied it to my local running copy of next
> though, which is what I was referring to.  I'll try to remember to
> push things like this in the future.

I've now `git am`'d and pushed on my development copy to
git://code.chass.utoronto.ca/bwalton-sup.git.  You should be able to
remerge the bw/bounce_message branch and get Adeodato's fix.

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/20090727/eb249faf/attachment.bin>


  parent reply	other threads:[~2009-07-27 16:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11 11:57 Adeodato Simó
2009-07-11 14:28 ` Ben Walton
2009-07-27 16:22   ` William Morgan
2009-07-27 16:25     ` Ben Walton
2009-07-27 16:29       ` William Morgan
2009-07-27 16:30       ` Ben Walton [this message]
2009-07-27 16:45         ` William Morgan
2009-07-27 16:30 ` 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=1248712092-sup-5843@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