<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array">
    <added>
      <filename>log/README</filename>
    </added>
  </added>
  <modified type="array"/>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>8f41aa9ff1dcf9e34b3731f3a0f49a9e2ae7aa96</id>
    </parent>
  </parents>
  <author>
    <name>Eric Kidd</name>
    <email>git@randomhacks.net</email>
  </author>
  <url>http://github.com/edavis10/mephisto/commit/28ec6c45c78a1bef8213aa020402b584e364fc73</url>
  <id>28ec6c45c78a1bef8213aa020402b584e364fc73</id>
  <committed-date>2008-12-01T05:41:22-08:00</committed-date>
  <authored-date>2008-12-01T05:39:44-08:00</authored-date>
  <message>Warning fix: Force the log/ directory to exist

When running 'rake', 'script/about', or any other command in fresh checkout
of Mephisto, Rails will display the following warning:

  Rails Error: Unable to access log file. Please ensure that
  /.../mephisto/log/development.log exists and is chmod 0666. The log
  level has been raised to WARN and the output directed to STDERR until
  the problem is fixed.

To fix this, the user must manually 'mkdir log'.  This problem occurs
because git doesn't allow empty directories to be checked into version
control, and because Rails 2.0 isn't smart enough to create the log/
directory when needed.

We can remove this file once Mephisto has been ported to Rails 2.2, which
knows how to create the log/ directory automatically.</message>
  <tree>e729eebfa1aa3d749ef132ab200e878791f60548</tree>
  <committer>
    <name>Eric Kidd</name>
    <email>git@randomhacks.net</email>
  </committer>
</commit>
