From: Dave Taht <dave.taht@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] is there a patch for tc-adv somewhere for showing active_flows
Date: Thu, 1 Oct 2015 15:31:58 +0200 [thread overview]
Message-ID: <CAA93jw7ggA5iLrGW7CT_fPezYwnf2ucqBFWh-X5Y5qA_T-O1dg@mail.gmail.com> (raw)
In-Reply-To: <560D2074.1070205@darbyshire-bryant.me.uk>
you now have commit access to both the sch_cake and tc-adv repos.
Anyone else want direct access?
On Thu, Oct 1, 2015 at 2:00 PM, Kevin Darbyshire-Bryant
<kevin@darbyshire-bryant.me.uk> wrote:
>
>
> On 30/09/15 12:28, Dave Taht wrote:
>> at the moment it seems best to keep working these out of tree versions, imho.
>
> The 'problem' with that Dave is that there are people here keen to be on
> the latest commits so that they may test the latest 'n' greatest code.
> Who doesn't want a willing set of fools^H^H^H^H^H^H testers trying to
> break code for free? :-)
>
> You've mentioned how great it is that things have been moving well
> recently, yes it is! I'd say that some of that is down to someone in
> essence doing a bit of janitorial work in collecting commits together
> and pushing them into a central-ish repo, namely yours. Personally
> speaking sending to your repo makes more sense as that's where the
> ceropackages repo points the openwrt users to go (well I think that's
> the case anyway)
>
> None of this is rocket surgery/brain science, somehow even I seem
> capable of merging repos/commits, but having some sort of idea in which
> repo active development is taking place so it can be collated & tested
> would be a very nice thing :-)
>
> From what I can work out at the moment, your github sch-cake repo is
> where you & JM work on the cake module, so hasn't diverged. JM appears
> to work on iproute/tc in Toke's iproute2 repo, but you work on
> iproute/tc in your github/tc-adv repo - they did diverge a little, with
> trivial merge conflicts. Are there any more? What have I missed?
>
> Apologies, I'm a little frustrated by other events at the moment and I
> think that may have spilled into this email as well....no hurt/insult
> intended.
>
> Kevin
>
>> On Wed, Sep 30, 2015 at 4:27 AM, Sebastian Moeller <moeller0@gmx.de> wrote:
>>> Jonathan,
>>>
>>> is Tokes repository the next best to master, or will all eventually accumulate in Dave’s repository? I just wonder which iproute2 to actually build on my test machine ;)
>>>
>>> Best Regards
>>> Sebastian
>>>
>>> On Sep 30, 2015, at 11:55 , Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
>>>
>>>> Dave,
>>>>
>>>> I've pulled the commits from Toke's iproute2 repo in which Jonathan is
>>>> placing his stats & other tweaks and sent you a pull request:
>>>> https://github.com/dtaht/tc-adv/pull/3 to get them into your tc-adv repo
>>>> (which is slightly more cero/openwrt facing)
>>>>
>>>> All the recent changes to cake & tc are running here.... livin' on the
>>>> bleeding edge :-)
>>>>
>>>> Kevin
>>>>
>>>>
>>>>
>>>> On 29/09/15 16:22, Jonathan Morton wrote:
>>>>> The big api change is in the stats output, which I'm still working
>>>>> on. As a stop gap, I have already pushed a version with both sparse
>>>>> and bulk flows reporting.
>>>>>
>>>>> The config api is inherently extensible.
>>>>>
>>>>> - Jonathan Morton
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Cake mailing list
>>>>> Cake@lists.bufferbloat.net
>>>>> https://lists.bufferbloat.net/listinfo/cake
>>>>
>>>> _______________________________________________
>>>> Cake mailing list
>>>> Cake@lists.bufferbloat.net
>>>> https://lists.bufferbloat.net/listinfo/cake
>>> _______________________________________________
>>> Cake mailing list
>>> Cake@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/cake
>>
>>
>
>
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2015-10-01 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 11:12 Dave Taht
2015-09-29 13:06 ` Kevin Darbyshire-Bryant
2015-09-29 13:15 ` Toke Høiland-Jørgensen
2015-09-29 13:24 ` Dave Taht
2015-09-29 13:27 ` Toke Høiland-Jørgensen
2015-09-29 14:22 ` Sebastian Moeller
2015-09-29 14:26 ` Dave Taht
2015-09-29 15:22 ` Jonathan Morton
2015-09-30 9:55 ` Kevin Darbyshire-Bryant
2015-09-30 10:06 ` Dave Taht
2015-09-30 11:27 ` Sebastian Moeller
2015-09-30 11:28 ` Dave Taht
2015-10-01 12:00 ` Kevin Darbyshire-Bryant
2015-10-01 13:31 ` Dave Taht [this message]
2015-10-01 14:17 ` Kevin Darbyshire-Bryant
2015-10-03 13:43 ` Dave Taht
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=CAA93jw7ggA5iLrGW7CT_fPezYwnf2ucqBFWh-X5Y5qA_T-O1dg@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