+invirt-remote (0.3.2) unstable; urgency=low
+
+ * Don't pass untrusted arguments to xm info.
+ * Exit with a non-0 error code on the host if there's an error.
+ * Always exec instead of fork&exec on the remctl server so that return
+ codes get passed on.
+
+ -- Evan Broder <broder@mit.edu> Sat, 31 Jan 2009 03:51:54 -0500
+
invirt-remote (0.3.1) unstable; urgency=low
* invirt.remote.bcast: provide stderr text when remctl fails