summaryrefslogtreecommitdiff
path: root/Porting/release_managers_guide.pod
diff options
context:
space:
mode:
authorJesse Vincent <jesse@bestpractical.com>2009-10-03 02:39:03 +0900
committerJesse Vincent <jesse@bestpractical.com>2009-10-03 03:28:47 +0900
commitb4d6b7c5c23218504515ce66d6416b98e769fdfc (patch)
treece6dd73fd29a1065d394483730ee51d303d7d913 /Porting/release_managers_guide.pod
parent07e28eecbce1dad6ffdda174732241d1e33136ce (diff)
downloadperl-b4d6b7c5c23218504515ce66d6416b98e769fdfc.tar.gz
fixing a typo in the release manager guide
Diffstat (limited to 'Porting/release_managers_guide.pod')
-rw-r--r--Porting/release_managers_guide.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/Porting/release_managers_guide.pod b/Porting/release_managers_guide.pod
index 60ef4efd4e..1e0851dcc9 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -309,7 +309,7 @@ Update the F<Changes> file to contain the git log command which would show
all the changes in this release. You will need assume the existence of a
not-yet created tag for the forthcoming release; e.g.
- git log ... perl-5.10.0..perl5.12.0
+ git log ... perl-5.10.0..perl-5.12.0
Due to warts in the perforce-to-git migration, some branches require extra
exclusions to avoid other branches being pulled in. Make sure you have the