[LTP] [PATCH 1/1] doc: Use man7.org also for git man pages

Petr Vorel pvorel@suse.cz
Wed Jan 14 12:50:20 CET 2026


https://man7.org/ has also git man pages (although slightly older than
on https://git-scm.com/), it's probably better than to have specific
config via extlinks for them.

Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
 doc/conf.py                           |  1 -
 doc/developers/test_case_tutorial.rst | 17 +++++++++--------
 doc/index.rst                         |  2 +-
 3 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/doc/conf.py b/doc/conf.py
index d49cb4e77e..bb6afcbe20 100644
--- a/doc/conf.py
+++ b/doc/conf.py
@@ -35,7 +35,6 @@ extlinks = {
     'repo': (f'{ltp_repo}/%s', '%s'),
     'master': (f'{ltp_repo}/blob/master/%s', '%s'),
     'shell_lib': (f'{ltp_repo}/blob/master/testcases/lib/%s', '%s'),
-    'git_man': ('https://git-scm.com/docs/git-%s', 'git %s'),
     # TODO: allow 2nd parameter to show page description instead of plain URL
     'kernel_doc': ('https://docs.kernel.org/%s.html', 'https://docs.kernel.org/%s.html'),
     'kernel_tree': ('https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/%s', '%s'),
diff --git a/doc/developers/test_case_tutorial.rst b/doc/developers/test_case_tutorial.rst
index f6495c4d72..08bd1b1519 100644
--- a/doc/developers/test_case_tutorial.rst
+++ b/doc/developers/test_case_tutorial.rst
@@ -58,8 +58,8 @@ test. At the time of writing there is no test for this call which was
 introduced in Linux kernel version 4.11.
 
 Linux system call specific tests are primarily contained in
-:master:`testcases/kernel/syscalls`, but you should also :git_man:`grep` the
-entire LTP repository to check for any existing usages of a system call.
+:master:`testcases/kernel/syscalls`, but you should also :manpage:`git-grep(1)`
+the entire LTP repository to check for any existing usages of a system call.
 
 One way to find a system call which is not currently tested by the LTP is to
 look at :kernel_tree:`include/linux/syscalls.h` in the Linux kernel tree.
@@ -252,8 +252,8 @@ to the below:
         smtpServer = smtp.server.address
 
 Obviously you need to at least change your name and e-mail. The SMTP server is
-useful for :git_man:`send-email`, which we will discuss later. The editor value is
-used for things like writing commits (without the ``-m`` option).
+useful for :manpage:`git-send-email(1)`, which we will discuss later. The
+editor value is used for things like writing commits (without the ``-m`` option).
 
 .. code-block:: bash
 
@@ -906,7 +906,7 @@ re-committing.
 
 You can also use ``edit`` and ``git commit --amend`` together to change a commit
 deep in your history, but without resetting the 'index'. The 'index' contains
-changes which you have staged with :git_man:`add`, but not yet committed.
+changes which you have staged with :manpage:`git-add(1)`, but not yet committed.
 
 So now that the commit history has been cleaned up, we need to submit a patch
 to the mailing list or make a pull request on GitHub. The mailing list is the
@@ -944,8 +944,8 @@ of the conflict. Usually, all you need to do is remove the lines you don't
 want, stage the changes and continue the ``rebase`` with ``git rebase
 --continue``.
 
-In order to create a patch e-mail we use :git_man:`format-patch`,
-we can then send that e-mail using :git_man:`send-email`.
+In order to create a patch e-mail we use :manpage:`git-format-patch(1)`,
+we can then send that e-mail using :manpage:`git-send-email(1)`.
 It is also possible to import the patch (``mbox``) file into a number of e-mail
 programs.
 
@@ -993,7 +993,8 @@ results. Once someone points out such an error it is usually obvious to
 everyone that it is a bug and needs to be fixed.
 
 Obviously testing the patch is one way of finding errors. You can apply patches
-using :git_man:`am`. Then it is just a case of compiling and running the tests.
+using :manpage:`git-am(1)`. Then it is just a case of compiling and running the
+tests.
 
 Finally, reading and attempting to comment on other peoples patches, gives
 you a better understanding of the reviewers perspective. This is better for
diff --git a/doc/index.rst b/doc/index.rst
index 06b75616fd..f78e7a4480 100644
--- a/doc/index.rst
+++ b/doc/index.rst
@@ -66,7 +66,7 @@ For developers
 .. descriptions here are active
 
 :doc:`developers/setup_mailinglist`
-   How to configure git and to start sending patches via :git_man:`send-email`.
+   How to configure git and to start sending patches via :manpage:`git-send-email(1)`.
 
 :doc:`developers/writing_tests`
    Starting guide on writing tests
-- 
2.51.0



More information about the ltp mailing list