Hi, Cheers!
Sorry too later!
I'll commit as soon as! :)
I'm using lb plugin in cloud loadbalance testing! and very interesting for your
plugin-cnat!
KANG
--Original--
From: "Nathan Skrzypczak";https://wiki.fd.io/view/DEV/Setting_up_Gerrit
[1]
Ole,
Auto-abandon is not auto-delete.
Abandoned patches remain accessible in gerrit and the 600+ patches which
would be auto-abandoned would continue to exist in virtually the same
state as they do today. Viewable by all and available to anyone
interested in utilizing them (i.e. restoring,
@Ole,
> What do you intend to happen with those 600+ abandonded changes in the future?
Clicking in gerrit on "restore" button, if you find a gold in there ;)
Peter Mikus
Engineer – Software
Cisco Systems Limited
From: vpp-dev@lists.fd.io on behalf of
Dave,
> To be perfectly honest, other than Andrew's proposal to tweak the
> auto-abandon parameters, I have not heard another solution that solves the
> problem of cleaning up the current queue and limiting the size of the queue
> in the future. Is anyone going to volunteer to manually
On Fri, Jan 29, 2021 at 6:09 PM Vratko Polak -X (vrpolak - PANTHEON
TECHNOLOGIES at Cisco) via lists.fd.io
wrote:
> > Why do you say that vpp_papi need to be dual licensed?
>
>
>
> I think e-mail reply would be long,
>
> and I will need to address comments anyway,
>
> so I respond via a Gerrit
Hi Murthy,
I am running with ASan on a regular basis and the vpp-debug-verify-master CI
job also runs it on per-commit basis, but as it is not a voting job, things
tend to deteriorate slowly until I picked it up again. I'd welcome any help
Can you check whether the issue is still present in
Hi folks,
right now it's rather hard to use the "ping" command over e.g. govpp as
it aborts immediately most of the time, usually upon receiving
SOCKET_READ_EVENT.
I've made a patch that makes ping stop only
on UNIX_CLI_PROCESS_EVENT_READ_READY / UNIX_CLI_PROCESS_EVENT_QUIT event,
so it does
Vratko,
> > Why do you say that vpp_papi need to be dual licensed?
>
> I think e-mail reply would be long,
> and I will need to address comments anyway,
> so I respond via a Gerrit change [1].
I didn't understand the argument made in that patch. Two points for originality
regarding choice of
