From: Dave Taht <dave.taht@gmail.com>
To: bismark-devel@lists.bufferbloat.net
Subject: Re: [Bismark-devel] some thoughts on continuous builds
Date: Tue, 26 Apr 2011 10:07:37 -0600 [thread overview]
Message-ID: <BANLkTimFk4MiM7CQd5BVDYY0LJOi7AY1mA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimxdWMBQYvsQUUD7oievGS+pti5Dg@mail.gmail.com>
An example of a bug that I would like to see isolated and fixed before
the next big development/Test cycle is:
http://www.bufferbloat.net/issues/88
As it would make it simpler to reflash devices with entirely new
firmware with a good backup.
Can someone take ownership of this one? Determine if it still exists,
and if it does, further bug report it to the openwrt folk at the very
least?
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
prev parent reply other threads:[~2011-04-26 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 15:35 Dave Taht
2011-04-26 15:37 ` Nick Feamster
2011-04-26 15:55 ` Dave Taht
2011-04-26 16:07 ` Dave Taht [this message]
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=BANLkTimFk4MiM7CQd5BVDYY0LJOi7AY1mA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bismark-devel@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