From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core66, updated. 2950a55ca44c453df12b60174396f00b69210423
Date: Sat, 16 Feb 2013 16:39:04 +0100 [thread overview]
Message-ID: <20130216153904.5EDFE200B6@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, core66 has been updated
via 2950a55ca44c453df12b60174396f00b69210423 (commit)
from eb7fff99fc287ed76ed39a3d408006bbcf0aabd4 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 2950a55ca44c453df12b60174396f00b69210423
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Feb 16 16:34:22 2013 +0100
QoS: remove noecn from fq_codel option.
ingress shaping need to drop some packets to limiting downloads.
-----------------------------------------------------------------------
Summary of changes:
config/qos/makeqosscripts.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/qos/makeqosscripts.pl b/config/qos/makeqosscripts.pl
index 8c4f77c..b623cbe 100644
--- a/config/qos/makeqosscripts.pl
+++ b/config/qos/makeqosscripts.pl
@@ -58,7 +58,7 @@ my $subclassfile = "/var/ipfire/qos/subclasses";
my $level7file = "/var/ipfire/qos/level7config";
my $portfile = "/var/ipfire/qos/portconfig";
my $tosfile = "/var/ipfire/qos/tosconfig";
-my $fqcodel_options = "noecn limit 800 quantum 500";
+my $fqcodel_options = "limit 800 quantum 500";
&General::readhash("${General::swroot}/ethernet/settings", \%netsettings);
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-02-16 15:39 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=20130216153904.5EDFE200B6@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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