From: "The IPFire Project." <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.13 Tech Preview - Fighting bufferbloat
Date: Thu, 06 Sep 2012 11:21:10 +0200 [thread overview]
Message-ID: <mailman.77.1346923283.808.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
Hello,
today, I would like to send you a link to a blog post about Codel, which
is available in the next release of IPFire:
http://planet.ipfire.org/post/ipfire-2-13-tech-preview-fighting-bufferbloat
We are still searching for testers for this release, as you can read
over here:
http://planet.ipfire.org/post/ipfire-2-13-testers-wanted
Thanks for your attention. I hope you enjoy the read.
Michael
reply other threads:[~2012-09-06 9:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.77.1346923283.808.ipfire-announce@lists.ipfire.org \
--to=ipfire-announce@lists.ipfire.org \
/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