General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: Ryan Mounce <ryan@mounce.com.au>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Win10 Updates vs cake
Date: Fri, 22 Dec 2017 08:07:21 -0500	[thread overview]
Message-ID: <601A1105-DC24-4EF3-A6EC-59155BAFAEB0@gmail.com> (raw)
In-Reply-To: <67EDDFE2-EFC6-4533-90A5-45171C426035@darbyshire-bryant.me.uk>

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

Kevin,

> Once the cake repo is sorted out I can redo & resubmit the patches for both master & 1701 - and with a bit of luck we’ll all be in an even place again.

Thanks for this update. I'm subscribed to the cake github stream, so I hear about changes there.

If I understand correctly, after those patches are resubmitted, 17.01 will have the newest cake with all bells/whistles. 

Would you post a note here to a) let us know when they're available, and b) how "normal people" (that is, non-developers) can get this newest code? (I'm happy to post instructions to the forum if no one beats me to it.) Thanks.

Rich

[-- Attachment #2: Type: text/html, Size: 1752 bytes --]

  reply	other threads:[~2017-12-22 13:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22  2:01 Rich Brown
2017-12-22  2:55 ` Ryan Mounce
2017-12-22  3:57   ` Ryan Mounce
2017-12-22  4:03     ` Jonathan Morton
2017-12-22  5:26     ` Jonathan Morton
2017-12-29  4:49       ` Ryan Mounce
2017-12-22  9:17     ` Kevin Darbyshire-Bryant
2017-12-22 13:07       ` Rich Brown [this message]
2017-12-28 17:48   ` Benjamin Cronce
2017-12-29  4:44     ` Ryan Mounce
2017-12-22  9:12 ` Mario Hock
     [not found] <mailman.56.1513933967.3659.bloat@lists.bufferbloat.net>
2017-12-22 13:13 ` Rich Brown

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=601A1105-DC24-4EF3-A6EC-59155BAFAEB0@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    --cc=ryan@mounce.com.au \
    /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