<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -1,5 +1,16 @@
 $Id$
 
+1.56_01 - Wed Feb  4 13:49:07 2009
+	* The cpan(1) client now exits with a non-zero value if it thinks
+	there were errors in the operation. I haven't tracked down every
+	spot where there can be errors from CPAN.pm though, so there might
+	be some cases where it still exits with 0 even though things 
+	failed.
+	* There is initial support for Log4perl, although you can't 
+	configure it yet. If you have Log4perl, cpan(1) uses it to print
+	to the screen. If you don't have Log4perl, it uses a minimal 
+	internal logger to do the same thing.
+
 1.54 - Sun Apr  6 15:53:26 2008
 	* Don't give a warning if the user is a Linux weenie who likes
 	to type &quot;install&quot;. Just ignore it an move on. It's still not</diff>
      <filename>Changes</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>36ca57414a29e1d4017615e5ec3c97524d352620</id>
    </parent>
  </parents>
  <author>
    <name>brian d foy</name>
    <email>brian@stonehenge.com</email>
  </author>
  <url>http://github.com/briandfoy/cpan-script/commit/bb85c0931d7d4179aaeb65c6bf86352e3c7a4b93</url>
  <id>bb85c0931d7d4179aaeb65c6bf86352e3c7a4b93</id>
  <committed-date>2009-02-04T11:51:44-08:00</committed-date>
  <authored-date>2009-02-04T11:51:44-08:00</authored-date>
  <message>* for version 1.56_01</message>
  <tree>b240f53da3daa2ea382830aad9d4264d4a9e1fbd</tree>
  <committer>
    <name>brian d foy</name>
    <email>brian@stonehenge.com</email>
  </committer>
</commit>
