From: Abigail Date: Fri, 9 Jan 2009 16:00:37 +0000 (+0100) Subject: Fixed some spelling errors X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=9469eb4a69f2671f0af6c58baf2e0a7e08975fc1;p=p5sagit%2Fp5-mst-13.2.git Fixed some spelling errors --- diff --git a/pod/perlrepository.pod b/pod/perlrepository.pod index 970d77c..d282c02 100644 --- a/pod/perlrepository.pod +++ b/pod/perlrepository.pod @@ -239,7 +239,7 @@ that you're on the I branch, and your repository is up to date: % git pull (It's preferable to patch against the latest blead version, since patches -are usually integrated from blead to the maintainance branches. This +are usually integrated from blead to the maintenance branches. This does not apply, obviously, in the rare case where your patch is specific to a maintaince release.) @@ -548,7 +548,7 @@ When the first bad commit is isolated, C will tell you so: Author: Dave Mitchell Date: Sat Feb 9 14:56:23 2008 +0000 - [perl #49472] Attributes + Unkown Error + [perl #49472] Attributes + Unknown Error ... bisect run success @@ -567,7 +567,7 @@ the "first commit where the bug is solved". C has much more information on how you can tweak your binary searches. -=head1 COMITTING TO MAINTENANCE VERSIONS +=head1 COMMITTING TO MAINTENANCE VERSIONS To commit to a maintenance version of perl, you need to create a local tracking branch: