Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt@lists.bufferbloat.net,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] [bug #442]
Date: Wed, 23 Jul 2014 22:48:43 -0700	[thread overview]
Message-ID: <CAA93jw5sOfFsVkrj1rdZ=AbvQOC416QBmv8tMGAELK1rc-_3SA@mail.gmail.com> (raw)

So far as I have heard the latest build IS more stable than anything
prior under conditions of low signal strength os OSX. (how's everyone
doing this week?)

I had long suspected we were actually seeing several bugs masquerading as one.

new hope:

https://dev.openwrt.org/changeset/41815

-- 
Dave Täht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article

             reply	other threads:[~2014-07-24  5:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24  5:48 Dave Taht [this message]
2014-07-24 12:07 ` Sebastian Moeller
  -- strict thread matches above, loose matches on Subject: below --
2014-07-13 17:44 [Cerowrt-devel] Bug 442? Sebastian Moeller

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='CAA93jw5sOfFsVkrj1rdZ=AbvQOC416QBmv8tMGAELK1rc-_3SA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cerowrt@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