From: John <john@pagonis.org>
To: rack-devel@googlegroups.com
Subject: Re: Deprecate Mongrel
Date: Thu, 11 Apr 2013 01:26:12 -0700 (PDT) [thread overview]
Message-ID: <1befdd84-2acd-4808-9322-18c6f2af2d65@googlegroups.com> (raw)
In-Reply-To: <0ae29f56-6862-4f13-a802-5ca975a53afc@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
Why deprecate something which works so well?
We're using Mongrel 1.2pre2 with Rack and we're very happy.
I mean if you have to break something due to new features, that would
demand a lot of work to support, then yes there is a case to be made.
Otherwise why do so?
/pagojo
--
---
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[-- Attachment #2: Type: text/html, Size: 1004 bytes --]
next prev parent reply other threads:[~2013-04-11 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 6:03 Deprecate Mongrel Vipul Amler
2013-04-11 8:26 ` John [this message]
2013-04-15 0:14 ` James Tucker
2013-04-15 22:26 ` John
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=1befdd84-2acd-4808-9322-18c6f2af2d65@googlegroups.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).