vpp - Vector Packet Processing

Age	Commit message (Expand)	Author	Files	Lines
2020-05-15	misc: removed executable bits from source files	Ray Kinsella	3	-0/+0
2020-03-23	sr: srv6 API cleanup	Jakub Grajciar	1	-11/+3
2020-02-26	sr: API cleanup	Jakub Grajciar	2	-47/+56
2020-02-18	misc: fix coverity warnings	Dave Barach	1	-1/+1
2020-01-10	sr: feature YAML files for Segment Routing	pcamaril	1	-0/+9
2019-12-10	api: multiple connections per process	Dave Barach	1	-1/+1
2019-04-08	fixing typos	Jim Thompson	1	-1/+1
2018-10-23	c11 safe string handling support	Dave Barach	3	-11/+11
2018-09-20	SR-MPLS: MPLS table checks (VPP-1422)	Neale Ranns	1	-0/+17
2018-09-14	Fix memory leak in API/CLI to create/modify SR policies	John Lo	2	-0/+4
2018-08-30	SR-MPLS: fixes and tests	Neale Ranns	1	-2/+19
2018-08-29	SR-mpls: do not pass empty label stack to fib	Neale Ranns	1	-10/+11
2018-03-29	Coverity fixes (VPP-1204)	Chris Luke	2	-12/+10
2018-03-09	MPLS Unifom mode	Neale Ranns	2	-6/+15
2018-01-23	VPPAPIGEN: vppapigen replacement in Python PLY.	Ole Troan	1	-2/+3
2018-01-09	VPP-1113 SR MPLS path.frp_label_stack	Pablo Camarillo	1	-17/+16
2017-12-18	SR-MPLS: binary API and automated steering	Pablo Camarillo	7	-484/+1658
2017-08-08	L2 over MPLS	Neale Ranns	2	-4/+4
2017-05-05	First commit SR MPLS	Pablo Camarillo	5	-0/+1283

All new inbound code contributions to the Project must be made using the Apache License, Version 2.0 (available here: https://www.apache.org/licenses/LICENSE-2.0) (the “Project License”). All new inbound code contributions must also be accompanied by a Developer Certificate of Origin (http://developercertificate.org) sign-off in the source code system that is submitted through a TSC-approved contribution process which will bind the authorized contributor and, if not self-employed, their employer to the applicable license; All outbound code will be made available under the Project License. Documentation will be received and made available by the Project under the Creative Commons Attribution 4.0 International License (available at http://creativecommons.org/licenses/by/4.0/). The Project may seek to integrate and contribute back to other open source projects (“Upstream Projects”). In such cases, the Project will conform to all license requirements of the Upstream Projects, including dependencies, leveraged by the Project. Upstream Project code contributions not stored within the Project’s main code repository will comply with the contribution process and license terms for the applicable Upstream Project.