On Wed, May 24, 2017 at 6:21 PM, Jon Loeliger wrote:
> On Wed, May 24, 2017 at 2:00 AM, wrote:
> > Hi Jon,
>
> Hi Ole,
>
> > Thanks for the poetry! ;-)
>
> Most welcome.
>
> > This is me in 01384fe
> > Apologies for that. Next time I see you let me bring both band aid and
> whiskey.
>
> Apology
On Wed, May 24, 2017 at 2:00 AM, wrote:
> Hi Jon,
Hi Ole,
> Thanks for the poetry! ;-)
Most welcome.
> This is me in 01384fe
> Apologies for that. Next time I see you let me bring both band aid and
> whiskey.
Apology accepted!
> To my excuse, there has been this list of "broken" APIs maint
Hi Jon,
Thanks for the poetry! ;-)
This is me in 01384fe
Apologies for that. Next time I see you let me bring both band aid and whiskey.
To my excuse, there has been this list of "broken" APIs maintained by the
Python and Java language binding implementors. It's been on the todo list for a
lon
,
John
-Original Message-
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Luke, Chris
Sent: Tuesday, May 23, 2017 4:40 PM
To: Jon Loeliger ; vpp-dev
Subject: Re: [vpp-dev] The Case Of the Missing API Definition
It's disappointing that no heads-u
prevent this in future. :)
Chris.
> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Jon Loeliger
> Sent: Tuesday, May 23, 2017 13:20
> To: vpp-dev
> Subject: [vpp-dev] The Case Of the Missing API Definitio
Folks,
I was causally walking down Update VPP Master Lane when I was
suddenly attacked from behind by a case of the missing API call!
I read vpp-dev mail daily, and I watch the Gerrit fervently, so I was
pretty sure I wouldn't be blind-sided by this sort of Silent Gotcha.
But there was no mistaki