From: "Rafael Mendonça França" <rafaelmfranca@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: [PATCH] README: remove yahns reference
Date: Tue, 12 Mar 2019 13:43:48 -0700 (PDT) [thread overview]
Message-ID: <6b05c821-d373-4a2a-9a49-5e59268639b1@googlegroups.com> (raw)
In-Reply-To: <20190312002656.wmgzpzfcjufiowie@dcvr>
[-- Attachment #1.1: Type: text/plain, Size: 1052 bytes --]
Thank you Eric,
applied in 9d25a133fa7651e60e23a46ef0b732fd131d3458.
On Monday, March 11, 2019 at 8:26:58 PM UTC-4, Eric Wong wrote:
>
> Given the fragile design of yahns and the scary (but honest)
> marketing of it; I've conceded it is unsuitable to mention in an
> introductory document such as the rack README.
> ---
> README.rdoc | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/README.rdoc b/README.rdoc
> index 83df7f42..883380c1 100644
> --- a/README.rdoc
> +++ b/README.rdoc
> @@ -37,7 +37,6 @@ These web servers include \Rack handlers in their
> distributions:
> * Reel
> * unixrack
> * uWSGI
> -* yahns
>
> Any valid \Rack app will run the same on all these handlers, without
> changing anything.
> --
> EW
>
--
---
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/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1458 bytes --]
prev parent reply other threads:[~2019-03-12 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 0:26 [PATCH] README: remove yahns reference Eric Wong
2019-03-12 20:43 ` Rafael Mendonça França [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=6b05c821-d373-4a2a-9a49-5e59268639b1@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).