Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: Ben Walton <bwalton@artsci.utoronto.ca>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Ruby 1.9 required for git next?
Date: Mon, 04 Jan 2010 14:47:12 -0500	[thread overview]
Message-ID: <1262634351-sup-4410@zyrg.net> (raw)
In-Reply-To: <1262633498-sup-2457@ntdws12.chass.utoronto.ca>

Excerpts from Ben Walton's message of 2010-01-04 14:32:09 -0500:
> Excerpts from Rich Lane's message of Mon Jan 04 14:00:51 -0500 2010:
> 
> > Those warnings are harmless. If you want to run with -w I suggest
> > redirecting stderr to a file.
> 
> Not on 1.8.5.  It was dying with an exception until I removed all
> instances of :BINARY.

Ok, I just sent in a patch that should fix this.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-01-04 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04 18:49 Mark Alexander
2010-01-04 18:58 ` Mark Alexander
2010-01-04 19:00 ` Rich Lane
2010-01-04 19:32   ` Ben Walton
2010-01-04 19:47     ` Rich Lane [this message]
2010-01-04 20:02       ` Ben Walton

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=1262634351-sup-4410@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=bwalton@artsci.utoronto.ca \
    --cc=sup-talk@rubyforge.org \
    /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