rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Christian Neukirchen <chneukirchen@gmail.com>
To: rack-devel@googlegroups.com
Subject: Re: rack-1.2.1 breaks with ruby 1.8.6
Date: Wed, 14 Jul 2010 18:39:57 +0200	[thread overview]
Message-ID: <877hkykof6.fsf@gmail.com> (raw)
In-Reply-To: <EB14FE2C-E672-4FBB-A259-3B356A6E8BD8@gmail.com> (James Tucker's message of "Wed, 14 Jul 2010 16:56:58 +0100")

James Tucker <jftucker@gmail.com> writes:

> On 14 Jul 2010, at 15:05, candlerb wrote:
>
>> Oops, I checked in git, and the ESCAPE_HTML fix is already in there.
>> Sorry for the noise.
>> 
>> The parenthesize warning still is present though, now at lib/rack/
>> server.rb line 233.
>
> Yeah, chris2, I know it's rapid, but can we roll a new release soon, pretty please? <3

I have zilch time before mid August.

-- 
Christian Neukirchen  <chneukirchen@gmail.com>  http://chneukirchen.org

  reply	other threads:[~2010-07-14 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14 14:01 rack-1.2.1 breaks with ruby 1.8.6 candlerb
2010-07-14 14:05 ` candlerb
2010-07-14 15:56   ` James Tucker
2010-07-14 16:39     ` Christian Neukirchen [this message]
2010-07-14 17:00       ` James Tucker

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877hkykof6.fsf@gmail.com \
    --to=rack-devel@googlegroups.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).