From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: Frank Horowitz <frank@horow.net>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Just FYI: WNDR3700 (v2???) refurbs available on Amazon for USD49.99
Date: Fri, 27 Feb 2015 18:07:28 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1502271806250.20700@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw58oFYraEigK7d48dHhB9ooH=yVGx1SMw_iUsNLjeJMLA@mail.gmail.com>
On Thu, 26 Feb 2015, Dave Taht wrote:
> We will hopefully get around to a cerowrt refresh fairly soon - as
> soon as some more test code lands - and do it on several platforms.
> Until then, try chaos calmer - and for all I know we will end up
> building more on openwrt directly this time rather than repeating all
> the stuff that openwrt won't take upstream that is presently in
> cerowrt.
you may have posted this and I'm just not remembering, but do you have a list of
what's in CeroWRT that OpenWRT won't take upstream (and any info on why they
won't take the items)?
Daivd Lang
next prev parent reply other threads:[~2015-02-28 2:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 18:15 Frank Horowitz
2015-02-26 18:44 ` Dave Taht
2015-02-28 2:07 ` David Lang [this message]
2015-02-28 3:27 ` Dave Taht
2015-02-28 4:44 ` David Lang
2015-02-28 15:25 ` [Cerowrt-devel] CeroWrt bits not in OpenWrt (renamed thread) Rich Brown
2015-02-28 16:47 ` Dave Taht
2015-02-28 21:41 ` David Lang
2015-02-28 23:58 ` David Lang
2015-03-12 16:43 ` Rich Brown
2015-03-12 20:31 ` Alan Jenkins
2015-03-12 20:43 ` Alan Jenkins
2015-03-12 21:21 ` Dave Taht
2015-03-13 0:53 ` Alan Jenkins
2015-03-13 15:00 ` Rich Brown
2015-03-12 21:47 ` Toke Høiland-Jørgensen
2015-03-12 21:59 ` Dave Taht
2015-03-13 15:26 ` Sebastian Moeller
2015-03-13 0:50 ` Alan Jenkins
2015-03-13 0:55 ` Sebastian Moeller
2015-03-13 1:35 ` David Lang
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=alpine.DEB.2.02.1502271806250.20700@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=frank@horow.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