From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/deBloat] 3b8470: Fixed unkind comment in the text.
Date: Tue, 06 Nov 2012 04:46:59 -0800 [thread overview]
Message-ID: <509906c341706_63861cb9ae880332@sh3.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/deBloat
Commit: 3b84707d5510d433f3ccc5d647715cf8ce35bb13
https://github.com/dtaht/deBloat/commit/3b84707d5510d433f3ccc5d647715cf8ce35bb13
Author: Dave Täht <dave.taht@bufferbloat.net>
Date: 2012-11-06 (Tue, 06 Nov 2012)
Changed paths:
M spec/rrule.doc
Log Message:
-----------
Fixed unkind comment in the text.
A really huge problem is that most of our tests test for the long term
behavior of tcp, when the real behavior is dozens or hundreds of short
sharded TCP connections and dns lookups. Looking REALLY hard at that,
is what is really needed in this test....
reply other threads:[~2012-11-06 12:47 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=509906c341706_63861cb9ae880332@sh3.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