X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=SubmittingPatches;h=d75518698645dc8b37f6b1c69082d99c64370eda;hb=79f108b14e7944ddc4669e9c03fc34b40a3a2288;hp=c16673fa97e89b0e401517e531c61ee0d9116ed7;hpb=8d62e151dd35645f9550b461144630d4f45d320e;p=sliver-openvswitch.git diff --git a/SubmittingPatches b/SubmittingPatches index c16673fa9..d75518698 100644 --- a/SubmittingPatches +++ b/SubmittingPatches @@ -1,7 +1,7 @@ How to Submit Patches for Open vSwitch ====================================== -Send changes to Open vSwitch as patches to discuss@openvswitch.org. +Send changes to Open vSwitch as patches to dev@openvswitch.org. One patch per email, please. More details are included below. If you are using Git, then "git format-patch" takes care of most of @@ -32,7 +32,7 @@ Testing is also important: - A patch that modifies Linux kernel code should be at least build-tested on various Linux kernel versions before - submission. I suggest versions 2.6.18, 2.6.27, and whatever + submission. I suggest versions 2.6.32 and whatever the current latest release version is at the time. - A patch that modifies the ofproto or vswitchd code should be @@ -102,7 +102,7 @@ Please sign off on the patch as a submitter, and be sure to have the author(s) sign off for patches that you did not author. Simply include your name and email address as the last line of the commit -messge before any comments (and author too, if that is not you): +message before any comments (and author too, if that is not you): Signed-off-by: Author Name Signed-off-by: Submitter Name @@ -156,7 +156,7 @@ files. Patch ----- -The patch should be in the body of the email following the descrition, +The patch should be in the body of the email following the description, separated by a blank line. Patches should be in "diff -up" format. We recommend that you use Git