Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] on me not being a bottleneck
Date: Sun, 18 Oct 2015 14:08:48 +0100	[thread overview]
Message-ID: <562399E0.7080603@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw6dXaOWjdTZtCq5YUHxhJ29qsrOM+2QJCXT8jMsZ57fKw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]



On 18/10/15 13:10, Dave Taht wrote:
> Any time I am being a bottleneck, please tell me in the subject line
> that I am being one?
>
> I have hopefully unified commiter access to the ceropackages,
> sch_cake, and tc_adv repos. If anyone else wants in, put your request
> in the subject line ,please.
Don't think you're the bottleneck :-)  JM has been putting in a few
sprints of activity (which is great) and I've been updating 'tc-adv'
after a quick openwrt 'trunk' sanity compile & test check.

Of course the world of openwrt & cerowrt don't pick up those latest
versions until 'ceropackages-3.10' gets updated with pointers to latest
commits - I did that this morning.

The only thing that I'm aware of that isn't now pointing to the latest
'bleeding edge' is both the 'sqm-scripts' pointers in
'ceropackages-3.10'(v1.0.2) and 'openwrt/packages'(v1.0.3)  However I
don't think there's anything desperately being missed by not being
there.  I don't know how happy Toke is in producing another release?

It feels like there's a real 'final push' being done here and it's great!


Kevin



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]

  reply	other threads:[~2015-10-18 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-18 12:10 Dave Taht
2015-10-18 13:08 ` Kevin Darbyshire-Bryant [this message]
2015-10-18 13:18 ` Sebastian Moeller

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=562399E0.7080603@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cake@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