Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Richard Brown <richard.e.brown@dartware.com>
To: "<cerowrt-devel@lists.bufferbloat.net>"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] CeroWrt 3.3.1-4
Date: Sat, 7 Apr 2012 02:28:40 +0000	[thread overview]
Message-ID: <EAA9DD1E-DEEA-4D9D-AE33-639D44E5257E@intermapper.com> (raw)
In-Reply-To: <mailman.127.1333680653.1801.cerowrt-devel@lists.bufferbloat.net>

Dave,

Congratulations on taming the wifi, adding CUBIC, and otherwise getting CeroWrt building and working again. Sorry you're still suffering with #113. Questions:

1) Is 3.3.1-4 worth posting for testing? I installed it and it seems to be operating fine. (DNS names *were* dead for a while after reboot. It seemed like only a couple minutes before the router began supplying them.) 

2) If 3.3.1-4 is good enough for testing, we should update the release notes. Let me know what has changed, and I'll update the page. http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_33_Release_Notes

I'm corresponding with Travis at OpenWrt to see what is necessary to devote the spares cycles on my quad-core box at home to the OpenWrt buildbot system. I'll let you know when there's something to report.

Best,

Rich

       reply	other threads:[~2012-04-07  2:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.127.1333680653.1801.cerowrt-devel@lists.bufferbloat.net>
2012-04-07  2:28 ` Richard Brown [this message]
2012-04-07  2:48   ` Dave Taht

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=EAA9DD1E-DEEA-4D9D-AE33-639D44E5257E@intermapper.com \
    --to=richard.e.brown@dartware.com \
    --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