From: Dave Rolsky <autarch@urth.org>
Date: Mon, 7 Sep 2009 17:21:38 +0000 (-0500)
Subject: Tweak formatting of pod so everything's an =item for next release
X-Git-Tag: 0.89_02~24
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=9b9a5a0799ca1377943e50892a72a36052ab3aa0;p=gitmo%2FMoose.git

Tweak formatting of pod so everything's an =item for next release
---

diff --git a/lib/Moose/Manual/Delta.pod b/lib/Moose/Manual/Delta.pod
index 98e4572..f1fa5ff 100644
--- a/lib/Moose/Manual/Delta.pod
+++ b/lib/Moose/Manual/Delta.pod
@@ -29,16 +29,18 @@ In particular, we now have C<reduce>, C<shuffle>, C<uniq>, and C<natatime>.
 Use C<with_meta> instead. The C<with_caller> option will start warning in a
 future release.
 
+=item Moose now warns if you call C<make_immutable> for a class with mutable ancestors
+
+This is dangerous because modifying a class after a subclass has been
+immutablized will lead to incorrect results in the subclass, due to inlining,
+caching, etc. This occasionally happens accidentally, when a class loads one
+of its subclasses in the middle of its class definition, so pointing out that
+this may cause issues should be helpful. Metaclasses (classes that inherit
+from L<Class::MOP::Object>) are currently exempt from this check, since at the
+moment we aren't very consistent about which metaclasses we immutablize.
+
 =back
 
-Moose now warns if you call C<make_immutable> for a class with mutable
-ancestors. This is dangerous because modifying a class after a subclass has
-been immutablized will lead to incorrect results in the subclass, due to
-inlining, caching, etc. This occasionally happens accidentally, when a class
-loads one of its subclasses in the middle of its class definition, so pointing
-out that this may cause issues should be helpful. Metaclasses (classes that
-inherit from L<Class::MOP::Object>) are currently exempt from this check, since
-at the moment we aren't very consistent about which metaclasses we immutablize.
 
 =head1 Version 0.89_01