summaryrefslogtreecommitdiff
path: root/Porting
diff options
context:
space:
mode:
authorTatsuhiko Miyagawa <miyagawa@bulknews.net>2010-10-19 16:52:38 +0900
committerTatsuhiko Miyagawa <miyagawa@bulknews.net>2010-10-19 16:53:24 +0900
commite43cb88f1ff82f838e94668572289d7e290d4bce (patch)
treeac88e176a74140681cb7f1b7b402f248b6fb778c /Porting
parent78f3c6825221f909e85e8dc3c862579483f92c53 (diff)
downloadperl-e43cb88f1ff82f838e94668572289d7e290d4bce.tar.gz
Fixed typo (double "with the") in release_managers_guide.pod
Diffstat (limited to 'Porting')
-rw-r--r--Porting/release_managers_guide.pod10
1 files changed, 5 insertions, 5 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 1c63f054ce..923a4fdb46 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: