From: Christoph Paasch <cpaasch at apple.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: Weekly meeting - 17 October 2019 16:00 UTC (9am PDT, 6pm CEST)
Date: Fri, 25 Oct 2019 16:46:38 -0700 [thread overview]
Message-ID: <20191025234638.GG62618@MacBook-Pro-64.local> (raw)
In-Reply-To: d2114f9d12535a997bf04a96aea5e1dbb9826c42.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
Hello,
On 24/10/19 - 14:51:08, Paolo Abeni wrote:
> Hi,
>
> On Wed, 2019-10-23 at 22:46 -0700, Christoph Paasch wrote:
> > I have a conflict tomorrow and can’t attend the meeting.
>
> Can you please give us an a brief update WRT mptcp.org support for
> MPTCP v1 via email?
I see in the minutes that you already discussed that and that Matthieu made
a branch with v1. I guess that unblocks you for now, right?
I am trying to find time to spend on Linux, but it's difficult at the
moment.
Christoph
>
> I'm especially interested in understanding when we can expect to test
> v1 vs mptcp.org.
>
> Thanks,
>
> Paolo
>
>
>
>
next reply other threads:[~2019-10-25 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 23:46 Christoph Paasch [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-24 12:51 [MPTCP] Re: Weekly meeting - 17 October 2019 16:00 UTC (9am PDT, 6pm CEST) Paolo Abeni
2019-10-24 5:46 Christoph Paasch
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191025234638.GG62618@MacBook-Pro-64.local \
--to=unknown@example.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.