From: Rich Brown <richb.hanover@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bufferbloat.net is sorely missed/Now it's back!
Date: Sat, 11 Jun 2016 15:24:47 -0400 [thread overview]
Message-ID: <E6A449E3-1317-43E4-8496-249DB328E33B@gmail.com> (raw)
In-Reply-To: <87inxfk28r.fsf@toke.dk>
Hi Toke,
> On Jun 11, 2016, at 2:29 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>>>
>>> Okay, updated the conversion to preserve the directory structure.
>>> Current version is here: https://kau.toke.dk/bufferbloat-archive. The
>>
>> I get a 404 on that right now across the board...
>>
>> https://kau.toke.dk/bufferbloat-archive/projects/codel/wiki/Benchmarking_Codel_and_FQ_Codel/
>
> Was moving things around and hadn't set up a redirect yet. Should work
> now, and the server also answers to www.bufferbloat.net. I did an
> nsupdate, but the linode nameservers don't seem to have picked it up
> yet. Not sure how to poke them to do so.
The new site just went live here in the shrubs of New Hampshire, USA. (It wasn't working ~10 minutes ago.)
WOW! This is a wonderful piece of work! It manages to regain most of the structure of the separate parts of the Redmine system.
I just forked the repo and will start looking for places to make it better. Thanks!
Rich
PS I will leave my placeholder github.io site up in case anyone wants to go back via the Wayback Machine. http://richb-hanover.github.io/bufferbloat-site/
next prev parent reply other threads:[~2016-06-11 19:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1225.1465559858.3642.bloat@lists.bufferbloat.net>
2016-06-10 15:27 ` [Bloat] bufferbloat.net is sorely missed Rich Brown
2016-06-10 15:47 ` Dave Taht
2016-06-10 16:19 ` Rich Brown
2016-06-10 17:08 ` Kevin Darbyshire-Bryant
2016-06-10 17:13 ` Outback Dingo
2016-06-10 18:05 ` Dave Taht
2016-06-10 18:17 ` Steinar H. Gunderson
2016-06-10 18:18 ` Rich Brown
2016-06-10 18:23 ` Dave Taht
2016-06-11 12:07 ` Toke Høiland-Jørgensen
2016-06-11 17:58 ` Dave Taht
2016-06-11 18:29 ` Toke Høiland-Jørgensen
2016-06-11 18:32 ` Toke Høiland-Jørgensen
2016-06-11 19:09 ` Dave Taht
2016-06-11 19:24 ` Rich Brown [this message]
2016-06-11 20:05 ` [Bloat] bufferbloat.net is sorely missed/Now it's back! Toke Høiland-Jørgensen
2016-06-11 21:31 ` Dave Taht
2016-06-12 17:49 ` [Bloat] Bufferbloat.net - Organizing, curating, and workflow Rich Brown
2016-06-12 18:02 ` Toke Høiland-Jørgensen
2016-06-12 18:13 ` moeller0
2016-06-12 18:16 ` Toke Høiland-Jørgensen
2016-06-12 18:24 ` moeller0
2016-06-12 18:25 ` Toke Høiland-Jørgensen
2016-06-12 18:27 ` Dave Taht
2016-06-12 18:33 ` Toke Høiland-Jørgensen
2016-06-13 13:25 ` Rich Brown
2016-06-13 14:05 ` Toke Høiland-Jørgensen
2016-06-13 15:13 ` [Bloat] Bufferbloat.net & LinkChecker Rich Brown
2016-06-13 19:18 ` Toke Høiland-Jørgensen
2016-06-13 14:58 ` [Bloat] Bufferbloat.net - Organizing, curating, and workflow Dave Taht
2016-06-13 15:15 ` Toke Høiland-Jørgensen
2016-06-13 15:39 ` Dave Taht
2016-06-13 10:33 ` [Bloat] bufferbloat.net is sorely missed/Now it's back! Kevin Darbyshire-Bryant
2016-06-13 11:10 ` Toke Høiland-Jørgensen
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E6A449E3-1317-43E4-8496-249DB328E33B@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=toke@toke.dk \
/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