Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	 make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] 89 things in draft
Date: Fri, 9 Sep 2016 11:36:35 -0700	[thread overview]
Message-ID: <CAA93jw5nz-g1Go_795JwFuwEEjt7gQT9VuHkzwP44hq7AEYY6g@mail.gmail.com> (raw)
In-Reply-To: <87r38t6iin.fsf@toke.dk>

On Fri, Sep 9, 2016 at 11:21 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Dave Taht <dave.taht@gmail.com> writes:
>
>> Well, from an *outlining* and "catchy title" perspective, I'm doing
>> well, but I just took a look at the backlog of things that I'd meant
>> to write, in
>>
>> https://github.com/dtaht/blog-cerowrt
>>
>> And 89 things are unfinished, 37000 words thus far. 28000 "finished"
>> words, at least.
>>
>> If I were to focus on finishing any of these concepts what would be of
>> most interest?
>
> Well...
>
>>   1450 flaws_in_flent.md
>
> ...definitely not this one ;)

Hah. That's one of the more finished ones (mostly just needs plots),
and despite the title... well... go read it.

> -Toke



-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

      reply	other threads:[~2016-09-09 18:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 18:15 Dave Taht
2016-09-09 18:21 ` Toke Høiland-Jørgensen
2016-09-09 18:36   ` Dave Taht [this message]

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=CAA93jw5nz-g1Go_795JwFuwEEjt7gQT9VuHkzwP44hq7AEYY6g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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