[Xen-changelog] [xen-4.1-testing] docs: correct formatting errors in xmdomain.cfg

[Xen patchbot-4.1-testing <patchbot@xxxxxxx>]

# HG changeset patch
# User Matt Wilson <msw@xxxxxxxxxx>
# Date 1352830096 0
# Node ID 8cd220183845b3428ad8e1cd0c3f4530312ea146
# Parent  700d0f03d50aa6619d313c1ff6aea7fd429d28a7
docs: correct formatting errors in xmdomain.cfg

This patch corrects the following errors produced by pod2man:

Hey! The above document had some coding errors, which are explained
below:

Around line 301:
    You can't have =items (as at line 305) unless the first thing after
    the =over is an =item

Around line 311:
    '=item' outside of any '=over'

Signed-off-by: Matt Wilson <msw@xxxxxxxxxx>
Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
Committed-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

xen-unstable changeset: 25840:c7e4b7e64303
Backport-requested-by: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Committed-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>

xen-4.2-testing changeset: 25885:c23d938e3e64
Backport-requested-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Committed-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
---


diff -r 700d0f03d50a -r 8cd220183845 docs/man/xmdomain.cfg.pod.5
--- a/docs/man/xmdomain.cfg.pod.5       Mon Oct 29 09:04:48 2012 +0100
+++ b/docs/man/xmdomain.cfg.pod.5       Tue Nov 13 18:08:16 2012 +0000
@@ -298,16 +298,14 @@ it holds, so that the new one may take t
 
 =back
 
+Additionally, the "on_crash" event can also take:
+
 =over 4
 
-Additionally, the "on_crash" event can also take:
-
 =item B<coredump-destroy>
 
 Dump the crashed domain's core and then destroy it.
 
-=back
-
 =item B<coredump-restart>
 
 Dump the crashed domain's core and then restart it.

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog