From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] babeld change
Date: Sun, 16 Jun 2013 14:15:33 -0700 [thread overview]
Message-ID: <CAA93jw7G29xxPjq7YcWSb=RsAu_G8jYNQ6pXSGQtz8DBSS+Ohw@mail.gmail.com> (raw)
There is a lot of interesting work coming up on babel, and I've not
got around to trying to merge the homenet work into quagga. I am
thinking of switching back (at least temporarily) to the standalone
babeld daemon rather than quagga-babeld to test out the algorithms
there. Any objections?
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next reply other threads:[~2013-06-16 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 21:15 Dave Taht [this message]
2013-06-16 21:47 ` Toke Høiland-Jørgensen
2013-06-16 21:55 ` Dave Taht
2013-06-16 22:04 ` Toke Høiland-Jørgensen
2013-06-16 22:08 ` [Cerowrt-devel] Field Report - installing 3.8.13-7 Rich Brown
2013-06-16 22:29 ` Toke Høiland-Jørgensen
2013-06-16 22:35 ` Dave Taht
2013-06-16 22:54 ` Rich Brown
2013-06-17 8:24 ` Toke Høiland-Jørgensen
2013-06-17 4:15 ` [Cerowrt-devel] babeld change Steven Barth
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='CAA93jw7G29xxPjq7YcWSb=RsAu_G8jYNQ6pXSGQtz8DBSS+Ohw@mail.gmail.com' \
--to=dave.taht@gmail.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