From: John <firstname.lastname@example.org> To: email@example.com Subject: Re: Deprecate Mongrel Date: Thu, 11 Apr 2013 01:26:12 -0700 (PDT) [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.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 firstname.lastname@example.org. 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 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 \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Deprecate Mongrel' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/rack.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).