Difference between revisions of "CSIT/Submitting Patches"
From fd.io
< CSIT
Dwallacelf (Talk | contribs) (Created page with "__TOC__ == Submitting Patches == The VPP wiki has a nice set of instructions for VPP/Pulling,_Building,_Running,_Hacking_and_Pushing_VPP_Code#Pushing_Code_with_git_review |...") |
Dwallacelf (Talk | contribs) (→Commit Message Headline Nomenclature) |
||
| Line 5: | Line 5: | ||
== Commit Message Headline Nomenclature == | == Commit Message Headline Nomenclature == | ||
| − | When committing code to the CSIT repository and pushing patches to gerrit, please add a prefix to the headline of the commit message that consists of | + | When committing code to the CSIT repository and pushing patches to gerrit, please add a prefix to the headline of the commit message that consists of |
| + | *<code>DO_NOT_MERGE:</code> | ||
| + | *<code>CSIT-<###>:</code> | ||
| + | * both ( <code>DO_NOT_MERGE CSIT-<###>:</code> ) | ||
| + | |||
| + | Here are some examples: | ||
CSIT-60: Create l2-vlan-dot1ad libraries for perf testing | CSIT-60: Create l2-vlan-dot1ad libraries for perf testing | ||
Revision as of 04:06, 1 July 2016
Submitting Patches
The VPP wiki has a nice set of instructions for Pushing Code with git review. The same process is recommended for submitting patches to the CSIT git repository.
Commit Message Headline Nomenclature
When committing code to the CSIT repository and pushing patches to gerrit, please add a prefix to the headline of the commit message that consists of
DO_NOT_MERGE:CSIT-<###>:- both (
DO_NOT_MERGE CSIT-<###>:)
Here are some examples:
CSIT-60: Create l2-vlan-dot1ad libraries for perf testing
DO_NOT_MERGE: test VXLAN + VLAN on newer version of VPP.
DO_NOT_MERGE CSIT-156: DPDK support for Nested VM image
Using this nomenclature makes the CSIT gerrit open patches list easier to manage for CSIT committers and code reviewers.
