+invirt-remote-server (0.1.1) unstable; urgency=low
+
+ * Now that we're doing real caching, cache for less time
+
+ -- Evan Broder <broder@mit.edu> Mon, 17 Nov 2008 13:18:23 -0500
+
+invirt-remote-server (0.1.0) unstable; urgency=low
+
+ * Add real caching to remconffs
+
+ -- Evan Broder <broder@mit.edu> Mon, 17 Nov 2008 13:05:32 -0500
+
+invirt-remote-server (0.0.18) unstable; urgency=low
+
+ * Add a "help" command for the control remctl
+
+ -- Evan Broder <broder@mit.edu> Sat, 15 Nov 2008 19:02:19 -0500
+
+invirt-remote-server (0.0.17) unstable; urgency=low
+
+ * Get the host with the most RAM based on the maximum recoverable
+ memory, not the memory currently available to Xen
+
+ -- Evan Broder <broder@mit.edu> Sat, 15 Nov 2008 10:30:10 -0500
+
+invirt-remote-server (0.0.16) unstable; urgency=low
+
+ * When returning from a bcast, put together the stdout, not the stderr
+
+ -- Evan Broder <broder@mit.edu> Mon, 10 Nov 2008 16:19:33 -0500
+
+invirt-remote-server (0.0.15) unstable; urgency=low
+
+ * Include invirt.remote Python module
+ * Ignore erroneous responses from a server if it's because the server is
+ down
+
+ -- Evan Broder <broder@mit.edu> Mon, 10 Nov 2008 15:19:28 -0500
+
invirt-remote-server (0.0.14) unstable; urgency=low
* Don't depend on invirt-mail-config
* shorten initscript with std-init, correct the usage message
- -- Greg Price <price@mit.edu> Wed, 5 Nov 2008 19:59:18 -0400
+ -- Greg Price <price@mit.edu> Wed, 05 Nov 2008 19:59:18 -0500
invirt-remote-server (0.0.11) unstable; urgency=low