From: Eric Wong <e@80x24.org>
To: unicorn-public@bogomips.org
Subject: TAN: Ragel now maintained by Colm networks
Date: Fri, 26 Jun 2015 19:46:27 +0000 [thread overview]
Message-ID: <20150626194627.GA12480@dcvr.yhbt.net> (raw)
As most of you know, unicorn has always used Ragel for HTTP
parsing (inherited from Mongrel).
For the most part, Ragel works great and does not need much
maintenance. I made some changes to work with the Ragel 5-to-6
transition for Mongrel (pre-unicorn) and that was it.
Since I mainly use Ragel from the Debian package nowadays,
I missed this bit of news when it was posted 2014-10-24.
http://www.colm.net/ragel-now-maintained-by-colm-networks/
| As of October 2014, Ragel will be maintained by Colm Networks.
| This is a new consulting company founded by Dr. Adrian D.
| Thurston.
(ed: Adrian Thurston is the original author of Ragel)
| Since we cannot operate in the open, the git repository for
| Ragel will no longer be available. The project will be
| published as release (and pre-release) tarballs only. On the
| upside, Ragel will get much more attention.
*Sigh* I guess we'll need to diff release tarballs from now on...
I'm not very knowledgeable in C++, so any extra help auditing Ragel
changes would be greatly appreciated.
| The license will remain the same: GPLv2 with an exception for
| the generated code derived from Ragel source.
OK, at least that is good to hear.
Fwiw, the ragel-users mailing list (where I lurked) closed in
July 2014, too.
Anyways, I still love Ragel as a tool/language and have used it
in other projects. For now, it seems to work, but I'm hesitant
to start new projects using it.
next reply other threads:[~2015-06-26 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 19:46 Eric Wong [this message]
2015-06-26 21:03 ` TAN: Ragel now maintained by Colm networks Bráulio Bhavamitra
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/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150626194627.GA12480@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=unicorn-public@bogomips.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/unicorn.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).