<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array">
    <added>
      <filename>.gitignore</filename>
    </added>
    <added>
      <filename>Rakefile</filename>
    </added>
    <added>
      <filename>VERSION.yml</filename>
    </added>
  </added>
  <modified type="array">
    <modified>
      <diff>@@ -4,11 +4,7 @@ Please see http://dash.fiveruns.com for an overview of the Dash service.
 
 == Summary
 
-Sensor provides a mechanism for &quot;external&quot; monitoring of infrastructure with Dash.
-Since Dash is usually embedded within an application (i.e. internal), there's no easy
-way to monitor things like Apache, memcached, or other pieces.  Sensor is designed to
-be installed on a machine and upload metrics for any infrastructure on that machine.
-The user just needs to configure which elements they want to monitor.
+Sensor provides a mechanism for &quot;external&quot; monitoring of infrastructure with Dash. Since Dash is usually embedded within an application (i.e. internal), there's no easy way to monitor things like Apache, memcached, or other pieces.  Sensor is designed to be installed on a machine and upload metrics for any infrastructure on that machine. The user just needs to configure which elements they want to monitor.
 
 == Installation
 
@@ -17,31 +13,22 @@ gem install fiveruns-dash-sensor -s http://gems.github.com
 == Configuration
 
 When you run 'fiveruns-dash-sensor' for the first time, it will create a blank
-configuration for you in ~/.fiveruns-dash-sensor/config.rb.  You will need to edit
-this file with your app token and activate the plugins for your environment.  Once
-done, you should be able to restart 'fiveruns-dash-sensor' for a few minutes to verify 
-everything is working as designed.  If there are no problems, you can run
-'fiveruns-dash-sensor -d' to spin off the daemon into the background and forget about it.
+configuration for you in ~/.fiveruns-dash-sensor/config.rb.  You will need to edit this file with your app token and activate the plugins for your environment.  Once done, you should be able to restart 'fiveruns-dash-sensor' for a few minutes to verify everything is working as designed.  If there are no problems, you can run 'fiveruns-dash-sensor -d' to spin off the daemon into the background and forget about it.
 
 == Command Summary
 
   fiveruns-dash-sensor --help
 
-Sensor allows you to control OS-specific parameters like log file and PID file location,
-the user and group to run as, etc.  -d will start Sensor as a daemon.  To stop it, just
-kill the associated PID.
+Sensor allows you to control OS-specific parameters like log file and PID file location, the user and group to run as, etc.  -d will start Sensor as a daemon.  To stop it, just kill the associated PID.
 
 == Creating your own Plugins
 
-Sensor allows you to create your own custom plugins for your own infrastructure.  Each
-plugin should reside in ~/.fiveruns-dash-sensor/&lt;name&gt;.rb and config.rb should have an
-entry in it like this:
+Sensor allows you to create your own custom plugins for your own infrastructure.  Each plugin should reside in ~/.fiveruns-dash-sensor/&lt;name&gt;.rb and config.rb should have an entry in it like this:
 
   sensor.plugin :&lt;name&gt;, any options here...
 
 Please see the existing plugins for examples of how your code should work.
 
-
 == License
 
   # (The FiveRuns License)</diff>
      <filename>README.rdoc</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>f70a575cd3a908c9b5defd6a7e6df06212fd6fe4</id>
    </parent>
  </parents>
  <author>
    <name>Bruce Williams</name>
    <email>bruce@codefluency.com</email>
  </author>
  <url>http://github.com/fiveruns/dash-sensor/commit/91fd50f3c02bf0ae6916b40b7eff81e7d0d7f445</url>
  <id>91fd50f3c02bf0ae6916b40b7eff81e7d0d7f445</id>
  <committed-date>2009-02-26T18:00:10-08:00</committed-date>
  <authored-date>2009-02-26T18:00:10-08:00</authored-date>
  <message>Version bump to 0.8.5</message>
  <tree>675fdd139561509f40027b43c728940d8d171123</tree>
  <committer>
    <name>Bruce Williams</name>
    <email>bruce@codefluency.com</email>
  </committer>
</commit>
