Merge branch 'mainstream'

[sliver-openvswitch.git] / SubmittingPatches

diff --git a/SubmittingPatches b/SubmittingPatches
index f454c3a..9b3dd9e 100644 (file)
--- a/SubmittingPatches
+++ b/SubmittingPatches
@@ -1,7 +1,7 @@
 How to Submit Patches for Open vSwitch
 ======================================
 
 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
 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
 
         - 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
           the current latest release version is at the time.
 
         - A patch that modifies the ofproto or vswitchd code should be


@@ -87,8 +87,8 @@ reader can see it for himself.
 
 If the patch refers to a commit already in the Open vSwitch
 repository, please include both the commit number and the subject of
 
 If the patch refers to a commit already in the Open vSwitch
 repository, please include both the commit number and the subject of

-the patch, e.g. 'commit 632d136c "vswitch: Remove restriction on
-datapath names."'.
+the patch, e.g. 'commit 632d136c (vswitch: Remove restriction on
+datapath names.)'.

 
 If you, the person sending the patch, did not write the patch
 yourself, then the very first line of the body should take the form
 
 If you, the person sending the patch, did not write the patch
 yourself, then the very first line of the body should take the form


@@ -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
 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 <author.name@email.address...>
 Signed-off-by: Submitter Name <submitter.name@email.address...>
 
 Signed-off-by: Author Name <author.name@email.address...>
 Signed-off-by: Submitter Name <submitter.name@email.address...>