This is an automated email from the git hooks/post-receive script.

guillem pushed a commit to branch main
in repository dpkg.

View the commit online:
https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=f9f715c3e75a30bb237a37ab9ba3c01deefde39e

commit f9f715c3e75a30bb237a37ab9ba3c01deefde39e
Author: Guillem Jover <guil...@debian.org>
AuthorDate: Fri Oct 20 01:55:17 2023 +0200

    man: Use L<> for manual page references
    
    This marks few more man page references that got missed due to
    containing characters not used in the search.
    
    Fixes: commit 1af074cf4b2b344e996c52cfdd34d0a6a90efbc1
    Changelog: silent
---
 man/deb-src-symbols.pod         | 2 +-
 man/dpkg-maintscript-helper.pod | 4 ++--
 man/dpkg.pod                    | 2 +-
 man/dselect.pod                 | 2 +-
 man/start-stop-daemon.pod       | 2 +-
 5 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/man/deb-src-symbols.pod b/man/deb-src-symbols.pod
index dcea7ab25..bcd21255b 100644
--- a/man/deb-src-symbols.pod
+++ b/man/deb-src-symbols.pod
@@ -229,7 +229,7 @@ At the moment, B<dpkg-gensymbols> supports three basic 
pattern types:
 =item B<c++>
 
 This pattern is denoted by the I<c++> tag. It matches only C++ symbols by
-their demangled symbol name (as emitted by B<c++filt>(1) utility). This
+their demangled symbol name (as emitted by L<c++filt(1)> utility). This
 pattern is very handy for matching symbols which mangled names might vary
 across different architectures while their demangled names remain the same. One
 group of such symbols is I<non-virtual thunks> which have architecture
diff --git a/man/dpkg-maintscript-helper.pod b/man/dpkg-maintscript-helper.pod
index e9079c914..1ac039da8 100644
--- a/man/dpkg-maintscript-helper.pod
+++ b/man/dpkg-maintscript-helper.pod
@@ -273,7 +273,7 @@ I<pathname>B<.dpkg-backup> back to I<pathname> if required.
 
 When using a packaging helper, please check if it has native
 B<dpkg-maintscript-helper> integration, which might make your life
-easier. See for example B<dh_installdeb>(1).
+easier. See for example L<dh_installdeb(1)>.
 
 Given that B<dpkg-maintscript-helper> is used in the B<preinst>,
 using it unconditionally requires a pre-dependency to ensure that the
@@ -329,4 +329,4 @@ B<never>.
 
 =head1 SEE ALSO
 
-B<dh_installdeb>(1).
+L<dh_installdeb(1)>.
diff --git a/man/dpkg.pod b/man/dpkg.pod
index 5146b70ac..89a957427 100644
--- a/man/dpkg.pod
+++ b/man/dpkg.pod
@@ -1577,7 +1577,7 @@ L<dpkg-deb(1)>,
 L<dpkg-query(1)>,
 L<deb(5)>,
 L<deb-control(5)>,
-B<dpkg.cfg>(5),
+L<dpkg.cfg(5)>,
 and
 L<dpkg-reconfigure(8)>.
 
diff --git a/man/dselect.pod b/man/dselect.pod
index 2c11acfbd..9f309074e 100644
--- a/man/dselect.pod
+++ b/man/dselect.pod
@@ -671,5 +671,5 @@ broken, it is also much more flexible than the built in 
access methods.
 
 L<dpkg(1)>,
 L<apt(8)>,
-B<sources.list>(5),
+L<sources.list(5)>,
 L<deb(5)>.
diff --git a/man/start-stop-daemon.pod b/man/start-stop-daemon.pod
index 25aaa1a12..639f5b38f 100644
--- a/man/start-stop-daemon.pod
+++ b/man/start-stop-daemon.pod
@@ -317,7 +317,7 @@ code for them to do this themselves.
 Wait for the background process to send a readiness notification before
 considering the service started (since version 1.19.3).
 This implements parts of the systemd readiness protocol, as specified
-in the B<sd_notify>(3) manual page.
+in the L<sd_notify(3)> manual page.
 The following variables are supported:
 
 =over

-- 
Dpkg.Org's dpkg

Reply via email to