Skip to content
Fetching contributors…
Cannot retrieve contributors at this time
82 lines (52 sloc) 2.29 KB
Revision history for Dist-Zilla-Plugin-ReadmeAnyFromPod
0.103520 2010-12-17 22:51:34 EST5EDT
- Added the ability to sepcify file name and format. Support for
three formats included: plaintext, markdown, and pod.
- Renamed to ReadmeAnyFromPod.
0.14 2010-09-17 20:38:55
- Set the META repository url to my github repo, as suggested
by avar. github user: Hercynium (sscaffidi)
0.13 2010-09-17 16:26:40
- Fixed failing test as per [CPAN RT: #60569] (sscaffidi)
0.12 2010-06-08 16:47:39
- Improvements by Kent Fredric to make the POD extraction
saner. The need for intermediary files was eliminited, which
allowed us to get rid of a call to sync(), which fails on
It still does the right thing with UTF-8, which was the reason
for the odd original code.
0.11 2010-05-26 12:53:27
- Convert this distro to use @AVAR
- Remove PodWeaver use in favor of hardcoded POD and improve
the documentation.
0.10 2010.05.01
Re-release due to Makefile.PL breakage caused by Dist::Zilla
0.09 2010.04.28
Integrate patch by Mark Gardner <> to make
t/gist-329018.t pass on Win32 and other architectures that
don't have IO::Handle::sync()
0.08 2010.04.11
Accidentally released 0.07 with commit
1abffc5f8711ba77cb27c9bda719da4590f0987e which replaced
Pod::Text with Pod::Readme. Pod::Readme is too broken to use
for the reasons detailed in the Git commit log.
0.07 2010.04.11
Bumped for re-release to CPAN (was deleted)
0.06 2010.03.11
Using in-memory filehandles as commited in 0.05 doesn't work
for some unknown reason. There's a TODO test for this
t/gist-329018.t now taken from
0.05 2010.03.11
Using IO::Scalar instead of Perl's built-in open() to open
in-memory filehandles breaks in-memory Pod::Text processing of
POD documents containing UTF-8 (who knows why) (avar)
0.04 2009.06.16
require Pod::Text 3.13
0.03 2009.05.10
can override README if it already has [Readme]
0.02 2009.4.5
0.01 2009.4.5
First version, released on an unsuspecting world.
Jump to Line
Something went wrong with that request. Please try again.