dev-manual: Updated the "Enabling and Using the Tool" section

The send-error-report tool syntax has slightly changed since the
documentation was written.  Removed the [server] part of the
command and added more detail on its use and results.

Reported-by: Michael Wood <michael.g.wood@intel.com>
(From yocto-docs rev: 10e28ab877b327301be536e5d515d5a419d082ac)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 22 insertions, 14 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 0ea494052e..147e0295ac 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -9877,28 +9877,36 @@
                 </literallayout>
                 Enabling error reporting causes the build process to collect
                 the errors and store them in a file as previously described.
-                When the build system encounters an error, it includes a command
-                as part of the console output.
+                When the build system encounters an error, it includes a
+                command as part of the console output.
                 You can run the command to send the error file to the server.
-                For example, the following command sends the errors to an upstream
-                server:
+                For example, the following command sends the errors to an
+                upstream server:
                 <literallayout class='monospaced'>
-     send-error-report /home/brandusa/project/poky/build/tmp/log/error-report/error_report_201403141617.txt [server]
+     $ send-error-report /home/brandusa/project/poky/build/tmp/log/error-report/error_report_201403141617.txt
+                </literallayout>
+                In the previous example, the errors are sent to a public
+                database available at
+                <ulink url='http://errors.yoctoproject.org'></ulink>, which is
+                used by the entire community.
+                If you specify a particular server, you can send the errors
+                to a different database.
+                Use the following command for more information on available
+                options:
+                <literallayout class='monospaced'>
+     $ send-error-report --help
                 </literallayout>
-                In the above example, the <filename>server</filename> parameter is
-                optional.
-                By default, the errors are sent to a database used by the entire
-                community.
-                If you specify a particular server, you can send them to a different
-                database.
             </para>
 
             <para>
-                When sending the error file, you receive a link that corresponds
-                to your entry in the database.
+                When sending the error file, you are prompted to review the
+                data being sent as well as to provide a name and optional
+                email address.
+                Once you satisfy these prompts, the command returns a link
+                from the server that corresponds to your entry in the database.
                 For example, here is a typical link:
                 <literallayout class='monospaced'>
-     http://localhost:8000/Errors/Search/1/158
+     http://errors.yoctoproject.org/Errors/Details/9522/
                 </literallayout>
                 Following the link takes you to a web interface where you can
                 browse, query the errors, and view statistics.