Setting tag sliver-openvswitch-2.2.90-1

[sliver-openvswitch.git] / REPORTING-BUGS

diff --git a/REPORTING-BUGS b/REPORTING-BUGS
index 8412ec6..86510d2 100644 (file)
--- a/REPORTING-BUGS
+++ b/REPORTING-BUGS
@@ -5,8 +5,17 @@ We are eager to hear from users about problems that they have
 encountered with Open vSwitch.  This file documents how best to report
 bugs so as to ensure that they can be fixed as quickly as possible.
 
-Please report bugs by sending email to bugs@openvswitch.org.  Include
-as much of the following information as you can in your report:
+Please report bugs by sending email to bugs@openvswitch.org.  
+
+The most important parts of your bug report are the following:
+
+       * What you did that make the problem appear.
+
+       * What you expected to happen.
+
+       * What actually happened.
+
+Please also include the following information:
 
         * The Open vSwitch version number (as output by "ovs-vswitchd
           --version").
@@ -16,27 +25,21 @@ as much of the following information as you can in your report:
 
         * Any local patches or changes you have applied (if any).
 
+The following are also handy sometimes:
+
         * The kernel version on which Open vSwitch is running (from
           /proc/version) and the distribution and version number of
           your OS (e.g. "Centos 5.0").
 
-        * The contents of the vswitchd configuration file (usually
-          /etc/ovs-vswitchd.conf).
+        * The contents of the vswitchd configuration database (usually
+          /etc/openvswitch/conf.db).
 
         * The output of "ovs-dpctl show".
 
         * If you have Open vSwitch configured to connect to an
           OpenFlow controller, the output of "ovs-ofctl show <bridge>"
           for each <bridge> configured in the vswitchd configuration
-          file.
-
-        * A description of the problem, which should include:
-
-                - What you did that make the problem appear.
-
-                - What you expected to happen.
-
-                - What actually happened.
+          database.
 
         * A fix or workaround, if you have one.