From 4a6cb83d334e391f85332ea38a2e467ac7743e4b Mon Sep 17 00:00:00 2001 From: Damjan Marion Date: Tue, 18 Sep 2018 18:41:38 +0200 Subject: rename vpp-dpdk-dev to vpp-ext-deps We need to have new tenants in the development package. This is first of series of patches which will allow us to have multiple external libs and tools packaged for developer's convenience. Change-Id: I884bd75fba96005bbf8cea92774682b2228e0e22 Signed-off-by: Damjan Marion --- dpdk/README | 34 ---------------------------------- 1 file changed, 34 deletions(-) delete mode 100644 dpdk/README (limited to 'dpdk/README') diff --git a/dpdk/README b/dpdk/README deleted file mode 100644 index 95154dc235f..00000000000 --- a/dpdk/README +++ /dev/null @@ -1,34 +0,0 @@ - -Changes needed to DPDK are stored here as git patch files. Maintaining these -files using “git format-patch” and “git am” will make it simpler to manage -these changes. Patches made to DPDK should only be temporary until they are -accepted upstream and made available in the next DPDK release. - -The following is the method used to generate these patches: - -1. Git clone the DPDK to a new directory: - # git clone http://dpdk.org/git/dpdk dpdk - -2. Create a branch based on the DPDK release you wish to patch. -Note, “git tag” will show you all the release tags. The following example is -for DPDK release tag “v2.2.0” and will create a branch named “two_dot_two”. - # cd dpdk - # git checkout -b two_dot_two v2.2.0 - -3. Apply all the existing VPP DPDK patches to this new branch. - # git am /dpdk/dpdk-2.2.0_patches/* - -4. Make your changes and commit your change to your DPDK repository. - # - # git commit -s - -5. Create the patch files with format-patch. This creates all the patch files -for your branch (two_dot_two), with your latest commits as the last ones. - # git format-patch master..two_dot_two - -6. Copy, add and commit the new patches into the VPP patches directory. - # cp /dpdk/dpdk-2.2.0_patches - # cd - # git add dpdk/dpdk-2.2.0_patches/ - # git commit -s - -- cgit 1.2.3-korg