In perl.git, the branch blead has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/a95b3d6ada665e29ff33e3063306726e5ec40338?hp=319b236e2ed58e5be687a549dd0b94342cacd751>

- Log -----------------------------------------------------------------
commit a95b3d6ada665e29ff33e3063306726e5ec40338
Author: Karl Williamson <[email protected]>
Date:   Fri Apr 22 13:00:22 2016 -0600

    Fix some pod errors
    
    These were discovered while testing the Pod::Checker that is intended to
    be used in 5.25.
-----------------------------------------------------------------------

Summary of changes:
 INSTALL                            | 10 +++++-----
 Porting/release_managers_guide.pod | 12 ++++++------
 README.synology                    |  6 +++---
 pod/perlguts.pod                   |  2 +-
 pod/perlop.pod                     |  4 ++--
 pod/perlrebackslash.pod            |  2 +-
 pod/perlvar.pod                    |  2 +-
 7 files changed, 19 insertions(+), 19 deletions(-)

diff --git a/INSTALL b/INSTALL
index affc9a8..55faf67 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1922,11 +1922,11 @@ specify which target environment to use, as well as 
C<ar> and friends:
 
 Additionally, a cross-compilation toolchain will usually install it's own
 logical system root somewhere -- that is, it'll create a directory
-somewhere which includes subdirectories like 'include' or 'lib'.  For
-example, you may end up with C</skiff/local/arm-linux>, where
-C</skiff/local/arm-linux/bin> holds the binaries for cross-compilation,
-C</skiff/local/arm-linux/include> has the headers, and
-C</skiff/local/arm-linux/lib> has the library files.
+somewhere which includes subdirectories like C<'include'> or C<'lib'>.  For
+example, you may end up with F</skiff/local/arm-linux>, where
+F</skiff/local/arm-linux/bin> holds the binaries for cross-compilation,
+F</skiff/local/arm-linux/include> has the headers, and
+F</skiff/local/arm-linux/lib> has the library files.
 If this is the case, and you are using a compiler that understands
 C<--sysroot>, like gcc or clang, you'll want to specify the
 C<-Dsysroot> option for Configure:
diff --git a/Porting/release_managers_guide.pod 
b/Porting/release_managers_guide.pod
index 6d67d0b..d2223f6 100644
--- a/Porting/release_managers_guide.pod
+++ b/Porting/release_managers_guide.pod
@@ -1483,19 +1483,19 @@ to ensure that the tarballs are available on the 
website.
 
 =item *
 
-Check C</src> on CPAN (on a fast mirror) to ensure that links to
-the new tarballs have appeared: There should be links in C</src/5.0>
+Check F</src> on CPAN (on a fast mirror) to ensure that links to
+the new tarballs have appeared: There should be links in F</src/5.0>
 (which is accumulating all new versions), and (for BLEAD-FINAL and
-MAINT only) an appropriate mention in C</src/README.html> (which describes
+MAINT only) an appropriate mention in F</src/README.html> (which describes
 the latest versions in each stable branch, with links).
 
-The C</src/5.0> links should appear automatically, some hours after upload.
-If they don't, or the C</src> description is inadequate,
+The F</src/5.0> links should appear automatically, some hours after upload.
+If they don't, or the F</src> description is inadequate,
 ask Ask <[email protected]>.
 
 =item *
 
-Check L<http://www.cpan.org/src/> to ensure that the C</src> updates
+Check L<http://www.cpan.org/src/> to ensure that the F</src> updates
 have been correctly mirrored to the website.
 If they haven't, ask Ask <[email protected]>.
 
diff --git a/README.synology b/README.synology
index c02a544..b1ef60b 100644
--- a/README.synology
+++ b/README.synology
@@ -189,12 +189,12 @@ commit 7a8f1212e5482613c8a5b0402528e3105b26ff24.
 
 =over 4
 
-=item C<ext/DynaLoader/t/DynaLoader.t>
+=item F<ext/DynaLoader/t/DynaLoader.t>
 
 One subtest fails due to the uncommon structure of the Synology file
-system. The file C</lib/glibc.so> is missing.
+system. The file F</lib/glibc.so> is missing.
 
-B<WARNING:> Do not symlink C</lib/glibc.so.6> to C</lib/glibc.so> or
+B<WARNING:> Do not symlink F</lib/glibc.so.6> to F</lib/glibc.so> or
 some system components will start to fail.
 
 =back
diff --git a/pod/perlguts.pod b/pod/perlguts.pod
index ba6cd16..42ebb8d 100644
--- a/pod/perlguts.pod
+++ b/pod/perlguts.pod
@@ -2742,7 +2742,7 @@ source, like this:
  =for apidoc sv_setiv
 
  Copies an integer into the given SV.  Does not handle 'set' magic.  See
- C<sv_setiv_mg>.
+ L<perlapi/sv_setiv_mg>.
 
  =cut
  */
diff --git a/pod/perlop.pod b/pod/perlop.pod
index 17d24bb..9b1319a 100644
--- a/pod/perlop.pod
+++ b/pod/perlop.pod
@@ -258,7 +258,7 @@ produces a warning unless you use S<C<no warnings 
'experimental::bitwise'>>.
 Unary C<"+"> has no effect whatsoever, even on strings.  It is useful
 syntactically for separating a function name from a parenthesized expression
 that would otherwise be interpreted as the complete list of function
-arguments.  (See examples above under L<Terms and List Operators (Leftward)>.)
+arguments.  (See examples above under L</Terms and List Operators (Leftward)>.)
 X<+>
 
 Unary C<"\"> creates a reference to whatever follows it.  See L<perlreftut>
@@ -1272,7 +1272,7 @@ in which case you might as well just use the more 
customary C<"||"> operator:
 
     open(HANDLE, "< :utf8", "filename") || die "Can't open: $!\n";
 
-See also discussion of list operators in L<Terms and List Operators 
(Leftward)>.
+See also discussion of list operators in L</Terms and List Operators 
(Leftward)>.
 
 =head2 Logical Not
 X<operator, logical, not> X<not>
diff --git a/pod/perlrebackslash.pod b/pod/perlrebackslash.pod
index f27da1f..3df9bd2 100644
--- a/pod/perlrebackslash.pod
+++ b/pod/perlrebackslash.pod
@@ -537,7 +537,7 @@ C<\b> when not immediately followed by a C<"{"> matches at 
any place
 between a word (something matched by C<\w>) and a non-word character
 (C<\W>); C<\B> when not immediately followed by a C<"{"> matches at any
 place between characters where C<\b> doesn't match.  To get better
-word matching of natural language text, see L<\b{wb}> below.
+word matching of natural language text, see L</\b{wb}> below.
 
 C<\b>
 and C<\B> assume there's a non-word character before the beginning and after
diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index 132c15e..1821b95 100644
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -1720,7 +1720,7 @@ from within the Win32 API.  Most Win32-specific code will 
report errors
 via C<$^E>.  ANSI C and Unix-like calls set C<errno> and so most
 portable Perl code will report errors via C<$!>.
 
-Caveats mentioned in the description of C<L<$!>> generally apply to
+Caveats mentioned in the description of C<L</$!>> generally apply to
 C<$^E>, also.
 
 This variable was added in Perl 5.003.

--
Perl5 Master Repository

Reply via email to