From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] : Deprecated the staqfq.lua script
Date: Tue, 10 Jan 2012 01:49:07 -0800 [thread overview]
Message-ID: <4f0c0993c95ab_2f023fe3154deaf812693f@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat
Commit: 4fb99df6b0de9fb7a854873c91561c2739e8aa02
https://github.com/dtaht/deBloat/commit/4fb99df6b0de9fb7a854873c91561c2739e8aa02
Author: Dave Taht <d@taht.net>
Date: 2012-01-09 (Mon, 09 Jan 2012)
Changed paths:
M src/staqfq.lua
Log Message:
-----------
Deprecated the staqfq.lua script
It had served it's purpose in testing qfq and sfq.
When I tried to extend it to handle other stuff...
it started getting ugly, fast.
It's replacement will be called 'debloat'.
But I will keep this script around for a while
Commit: 5245bf0eac2ed121b0a64563c7b5b091e916f5f3
https://github.com/dtaht/deBloat/commit/5245bf0eac2ed121b0a64563c7b5b091e916f5f3
Author: Dave Taht <d@taht.net>
Date: 2012-01-10 (Tue, 10 Jan 2012)
Changed paths:
A src/cerowrt.conf
A src/debloat
A src/man/debloat.mdwn
M src/qmodels/sfq.lua
Log Message:
-----------
New, improved 'debloat' script that does more stuff, more cleanly
Still is showing it's heritage as a shell script...
does a few more qdiscs now, not necessarily correctly, I
have to think about how to manage the depths right in this arch.
Commit: e24ff88d52635498437d2f16296d5f2f1b62551c
https://github.com/dtaht/deBloat/commit/e24ff88d52635498437d2f16296d5f2f1b62551c
Author: Dave Taht <d@taht.net>
Date: 2012-01-10 (Tue, 10 Jan 2012)
Changed paths:
M src/debloat
Log Message:
-----------
openwrt fix
Compare: https://github.com/dtaht/deBloat/compare/8d025cc...e24ff88
reply other threads:[~2012-01-10 9:49 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=4f0c0993c95ab_2f023fe3154deaf812693f@sh1.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@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