From: Dave Taht <dave.taht@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] github sch_cake - safe for pull requests?
Date: Tue, 6 Oct 2015 23:09:49 +0200 [thread overview]
Message-ID: <CAA93jw7_=cfOSOBz6dzT7JWSiF+roGoyESx9fOhk3GwF+rpnJg@mail.gmail.com> (raw)
In-Reply-To: <56143510.1070606@darbyshire-bryant.me.uk>
yes, I was too buried to work on the api changes. pull and merge away!
On Tue, Oct 6, 2015 at 10:54 PM, Kevin Darbyshire-Bryant
<kevin@darbyshire-bryant.me.uk> wrote:
> Hi Dave et al,
>
> Spotted a couple of minor typos in sch_cake post checkpatch cleanup.
> Are you happy for pull requests & merges or are you still in a
> 'lockdown' for purposes of API/ABI changes?
>
>
> Kevin
>
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
--
Dave Täht
Do you want faster, better, wifi? https://www.patreon.com/dtaht
prev parent reply other threads:[~2015-10-06 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 20:54 Kevin Darbyshire-Bryant
2015-10-06 21:09 ` 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
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='CAA93jw7_=cfOSOBz6dzT7JWSiF+roGoyESx9fOhk3GwF+rpnJg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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