From: "Matthias Wächter" <matthias@waechter.wiz.at>
To: rack-devel@googlegroups.com
Subject: Re: Purpose of config.ru (regarding server options), #245
Date: Wed, 21 Dec 2011 10:08:18 +0100 [thread overview]
Message-ID: <4EF1A202.8050600@waechter.wiz.at> (raw)
In-Reply-To: <4EAB1844.7060506@waechter.wiz.at>
Hi Rack community,
On 28.10.2011 23:01, Matthias Wächter wrote:
> https://github.com/typingArtist/rack/commit/a10b227c32c061fb18e42204bb6da07e237c80ad
> https://github.com/typingArtist/rack/commit/0fd5b873de2096bb1b9e83e6f41fb5ed62ea8632
Can I ask once more what’s wrong with this addition? It doesn’t hurt
anyone using Rack now, and it removes the burden to write a separate
binary just for calling rackup with the right options, like suggested in
analogy to Thin. It is clear Ruby, no magic, no nothing.
Please, don’t ask me to maintain my own branch just for this stuff, please!
– Matthias
prev parent reply other threads:[~2011-12-21 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 11:25 Purpose of config.ru (regarding server options), #245 Matthias Wächter
2011-10-02 11:46 ` coolesting
2011-10-02 23:20 ` James Tucker
2011-10-03 8:52 ` Christian Neukirchen
2011-10-29 1:06 ` Matthias Wächter
2011-10-28 21:01 ` Matthias Wächter
2011-12-21 9:08 ` Matthias Wächter [this message]
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=4EF1A202.8050600@waechter.wiz.at \
--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).