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

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

# HG changeset patch
# User Matt Wilson <msw@xxxxxxxxxx>
# Date 1351266012 -3600
# Node ID c23d938e3e6401e75b0b11e04f9c7815208dd906
# Parent  cd0ae0ba4653ab4d35a8b06db6e0a40b65065575
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>
---


diff -r cd0ae0ba4653 -r c23d938e3e64 docs/man/xmdomain.cfg.pod.5
--- a/docs/man/xmdomain.cfg.pod.5       Fri Oct 26 16:40:05 2012 +0100
+++ b/docs/man/xmdomain.cfg.pod.5       Fri Oct 26 16:40:12 2012 +0100
@@ -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