From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============4724151676678522815=="
MIME-Version: 1.0
From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] [PATCH MPTCP 0/2] mptcp: token api refactoring/cleanup
Date: Wed, 04 Sep 2019 14:01:25 +0200
Message-ID: <20190904120125.GI13660@breakpoint.cc>
In-Reply-To: 8897dad2-c864-01cc-ee30-639ebbe956b9@tessares.net
X-Status: 
X-Keywords:                  
X-UID: 1791

--===============4724151676678522815==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Matthieu Baerts <matthieu.baerts(a)tessares.net> wrote:
> >> That has to happen :/
> > =

> > Why?
> =

> I was suspecting that with the all the squashes and rebase we did and
> continue to do. If we do not monitor this, we will have more issues :)
> On my side, I don't compile each commit we export.

Argh, ok, sorry -- I misunderstood what you said :-)
Until we go upstream with this the intermediate breakage is fine of
course, no need to do anything right now.

Thanks for the pad update!

--===============4724151676678522815==--