From: Pete Heist <pete@heistp.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] the Cake stalemate
Date: Tue, 19 Jun 2018 12:04:18 +0200 [thread overview]
Message-ID: <FF91EA2E-81B1-4759-A806-FBFDC1B4FCD1@heistp.net> (raw)
In-Reply-To: <87in6ft81g.fsf@toke.dk>
> On Jun 19, 2018, at 11:55 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Pete Heist <pete@heistp.net> writes:
>
>> Whether or not it helps with the upcoming talk or future plans, I’m
>> thinking about the most recent experience with trying to upstream Cake
>> and how to break the stalemate.
>
> Not sure there is a stalemate, actually. I just ran out of time to do
> further revisions; planning to take that up again. Don't see any reason
> why we shouldn't be able to succeed in getting Cake upstream in its
> current form(ish) in just a few more revisions (or, who knows, maybe a
> dozen more; better not jinx it ;)).
Ah, ok, so I may have mis-interpreted some of the “we won’t accept it unless” statements, which I got lost in. :)
Then just take the rest of it as other thoughts for when there’s time / energy…
next prev parent reply other threads:[~2018-06-19 10:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 9:31 Pete Heist
2018-06-19 9:55 ` Toke Høiland-Jørgensen
2018-06-19 10:04 ` Pete Heist [this message]
2018-06-19 11:32 ` Jonathan Morton
2018-06-19 11:54 ` Toke Høiland-Jørgensen
2018-06-19 12:26 ` Pete Heist
2018-06-19 13:41 ` Kevin Darbyshire-Bryant
2018-06-19 14:48 ` Pete Heist
2018-06-19 16:24 ` Dave Taht
2018-06-19 20:14 ` Pete Heist
2018-06-19 20:35 ` Jonathan Morton
2018-06-19 21:48 ` Dave Taht
2018-06-19 23:41 ` Sebastian Moeller
2018-06-19 22:34 ` Pete Heist
2018-06-19 23:38 ` Sebastian Moeller
2018-06-20 3:36 ` Jonathan Morton
2018-06-20 4:34 ` Sebastian Moeller
2018-06-19 12:08 ` Pete Heist
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=FF91EA2E-81B1-4759-A806-FBFDC1B4FCD1@heistp.net \
--to=pete@heistp.net \
--cc=cake@lists.bufferbloat.net \
--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