In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/e43cb88f1ff82f838e94668572289d7e290d4bce?hp=78f3c6825221f909e85e8dc3c862579483f92c53>
- Log ----------------------------------------------------------------- commit e43cb88f1ff82f838e94668572289d7e290d4bce Author: Tatsuhiko Miyagawa <[email protected]> Date: Tue Oct 19 16:52:38 2010 +0900 Fixed typo (double "with the") in release_managers_guide.pod ----------------------------------------------------------------------- Summary of changes: Porting/release_managers_guide.pod | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod index 1c63f05..923a4fd 100644 --- a/Porting/release_managers_guide.pod +++ b/Porting/release_managers_guide.pod @@ -315,11 +315,11 @@ this line in README.vms needs special handling: rename perl-5^.10^.1.dir perl-5_10_1.dir When doing a blead release, also make sure the C<PERL_API_*> constants in -F<patchlevel.h> are in sync with the with the version you're releasing, unless -you're absolutely sure the release you're about to make is 100% binary -compatible to an earlier release. When releasing a stable perl version, the -C<PERL_API_*> constants C<MUST NOT> be changed as we aim to guarantee binary -compatibility in maint branches. +F<patchlevel.h> are in sync with the version you're releasing, unless you're +absolutely sure the release you're about to make is 100% binary compatible +to an earlier release. When releasing a stable perl version, the C<PERL_API_*> +constants C<MUST NOT> be changed as we aim to guarantee binary compatibility +in maint branches. Commit your changes: -- Perl5 Master Repository
