Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] OpenWrt Chaos Calmer final release available
Date: Fri, 11 Sep 2015 17:07:11 -0600	[thread overview]
Message-ID: <CAK-n8j4sU2aDCOs4bCD-NJLXNV84COPqg7d4hEYksD6UQqGD7w@mail.gmail.com> (raw)

The OpenWrt developers are proud to announce the final release of
OpenWrt Chaos Calmer.

    https://openwrt.org/

===

How much work is involved in getting an updated build of CeroWRT built
on top of Chaos Calmer 15.05?

I have to admit that the previous (only) release of CeroWRT from late
June has been pretty darn stable!

Thanks - Jim

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

             reply	other threads:[~2015-09-11 23:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11 23:07 Jim Reisert AD1C [this message]
2015-09-12 10:13 ` Robert Bradley

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://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAK-n8j4sU2aDCOs4bCD-NJLXNV84COPqg7d4hEYksD6UQqGD7w@mail.gmail.com \
    --to=jjreisert@alum.mit.edu \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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