From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: Rainbows! list <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Subject: Re: [PATCH] Remove deprecated Rainbows::HttpResponse
Date: Fri, 5 Aug 2011 16:51:44 -0700 [thread overview]
Message-ID: <20110805235144.GA27634@dcvr.yhbt.net> (raw)
In-Reply-To: <CADtcy21gt2YbEjET5GcqFHCxtRvsjxheFaz+E+XWJoBOOBKZFw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Pratik <pratiknaik-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On 5 August 2011 23:07, Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org> wrote:
> > I suppose I can release the current rainbows.git as Rainbows! 4.2.0
> > today (a good version number :D) just for Cramp.
>
> Perfect. I just released cramp 0.14. Waiting for Rainbows! 4.2.0 :)
Just released 4.2.0 and have HttpResponse removal queued up for 4.3.0.
I suppose Cramp has a smallish userbase and nobody's going to be
stuck on 0.13 and unable to upgrade, right?
--
Eric Wong
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2011-08-05 23:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 21:24 [PATCH] Remove deprecated Rainbows::HttpResponse Pratik Naik
[not found] ` <1312579461-17223-1-git-send-email-pratiknaik-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-08-05 22:07 ` Eric Wong
[not found] ` <20110805220714.GA6456-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2011-08-05 22:27 ` Pratik
[not found] ` <CADtcy21gt2YbEjET5GcqFHCxtRvsjxheFaz+E+XWJoBOOBKZFw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-08-05 23:51 ` Eric Wong [this message]
[not found] ` <20110805235144.GA27634-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2011-08-06 15:20 ` Pratik
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
List information: https://yhbt.net/rainbows/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110805235144.GA27634@dcvr.yhbt.net \
--to=normalperson-rmlxzr9ms24@public.gmane.org \
--cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/rainbows.git/
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).