Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Richard O <rocon46@hotmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt-3.10.36-6 released
Date: Sun, 20 Apr 2014 07:37:00 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140420T083604-402@post.gmane.org> (raw)
In-Reply-To: <CAA93jw5btdZNKKKQpAh-tLB3Gxk7A5DNVCTcHjbbEuWBH64M6Q@mail.gmail.com>

Dave Taht <dave.taht <at> gmail.com> writes:

> 
> If you are not experiencing problems with wifi or with heartbleed
> there are few reasons to update to this release.
> 

 

I've been running 3.10.34-4 for awhile now and haven't run into any issues,
wifi or not.

Is there any other reasons to upgrade aside from heartbleed and DNSSEC?

Also, does this release use simplest.qos on inbound? I am hesitant to
upgrade solely for this reason.


  reply	other threads:[~2014-04-20  7:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19 20:01 Dave Taht
2014-04-20  7:37 ` Richard O [this message]
2014-04-21 19:10   ` Dave Taht
2014-04-20 20:46 ` Sebastian Moeller
2014-04-21 19:09   ` Dave Taht
2014-04-21 19:18     ` Sebastian Moeller
2014-04-21 19:42       ` Dave Taht
2014-04-21 21:34         ` 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=loom.20140420T083604-402@post.gmane.org \
    --to=rocon46@hotmail.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