From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages-3.10] b7e766: kmod-sched-fq_pie: add support for fq_pie schedule...
Date: Sat, 02 May 2015 01:13:54 -0700 [thread overview]
Message-ID: <55448742a8f10_eb13fc16a16b2bc697b@hookshot-fe6-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages-3.10
Commit: b7e766a1d0b3053fa49586b23d7e9921beaefe8d
https://github.com/dtaht/ceropackages-3.10/commit/b7e766a1d0b3053fa49586b23d7e9921beaefe8d
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2015-05-02 (Sat, 02 May 2015)
Changed paths:
A net/kmod-sched-fq_pie/Makefile
Log Message:
-----------
kmod-sched-fq_pie: add support for fq_pie scheduler
Commit: 0b2b8f6fe40dc82f8837fb11394ebfaa8fedf59e
https://github.com/dtaht/ceropackages-3.10/commit/0b2b8f6fe40dc82f8837fb11394ebfaa8fedf59e
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2015-05-02 (Sat, 02 May 2015)
Changed paths:
M net/kmod-sched-fq_pie/Makefile
Log Message:
-----------
sched_fq_pie: corrected repo name
Compare: https://github.com/dtaht/ceropackages-3.10/compare/3ab9dcdbd3af...0b2b8f6fe40d
reply other threads:[~2015-05-02 8:13 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=55448742a8f10_eb13fc16a16b2bc697b@hookshot-fe6-cp1-prd.iad.github.net.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