[Xen-changelog] [xen-unstable] docs: Say in xm(1) that xm is obsolete

[Xen patchbot-unstable <patchbot@xxxxxxx>]

# HG changeset patch
# User Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
# Date 1323363300 0
# Node ID 37c83706e0744a319fff61900b245ad8226c108f
# Parent  52819464e67d871e4a17ae4038be115a73a32e9f
docs: Say in xm(1) that xm is obsolete

Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
---


diff -r 52819464e67d -r 37c83706e074 docs/man/xm.pod.1
--- a/docs/man/xm.pod.1 Thu Dec 08 16:40:09 2011 +0000
+++ b/docs/man/xm.pod.1 Thu Dec 08 16:55:00 2011 +0000
@@ -1,6 +1,6 @@
 =head1 NAME
 
-xm - Xen management user interface
+xm - Obsolete xen management user interface
 
 =head1 SYNOPSIS
 
@@ -8,10 +8,14 @@
 
 =head1 DESCRIPTION
 
-The B<xm> program is the main interface for managing Xen guest
-domains. The program can be used to create, pause, and shutdown
-domains. It can also be used to list current domains, enable or pin
-VCPUs, and attach or detach virtual block devices.
+This program is now superseded by B<xl>, which should be largely
+backwards-compatible with B<xm>.
+
+The B<xm> program is the main interface for managing Xen guest domains
+when the obsolete Xend toolstack is in use. The program can be used to
+create, pause, and shutdown domains. It can also be used to list
+current domains, enable or pin VCPUs, and attach or detach virtual
+block devices.
 
 The basic structure of every B<xm> command is almost always:
 

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