From 6f10f4b476fc7d049b3983c55bf59f2e7b6247c2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Franc=C3=ADlio=20Ara=C3=BAjo?= Date: Wed, 7 Jan 2026 10:20:06 -0300 Subject: [PATCH 1/2] Fix libgit2 links --- book/B-embedding-git/sections/libgit2.asc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/B-embedding-git/sections/libgit2.asc b/book/B-embedding-git/sections/libgit2.asc index 2e006fdc0..38a510a65 100644 --- a/book/B-embedding-git/sections/libgit2.asc +++ b/book/B-embedding-git/sections/libgit2.asc @@ -233,5 +233,5 @@ pygit2.Repository("/path/to/repo") # open repository ==== Further Reading Of course, a full treatment of Libgit2's capabilities is outside the scope of this book. -If you want more information on Libgit2 itself, there's API documentation at https://libgit2.github.com/libgit2[^], and a set of guides at https://libgit2.github.com/docs[^]. +If you want more information on Libgit2 itself, there's API documentation at https://libgit2.org/docs/reference/main/[^], and a set of guides at https://libgit2.org/docs/[^]. For the other bindings, check the bundled README and tests; there are often small tutorials and pointers to further reading there. From 6794bb9505d70fe1d26ddedb3c5a4292259b26a7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Franc=C3=ADlio=20Ara=C3=BAjo?= Date: Wed, 7 Jan 2026 10:20:33 -0300 Subject: [PATCH 2/2] Fix Git Maintainer's guide link --- book/05-distributed-git/sections/maintaining.asc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/05-distributed-git/sections/maintaining.asc b/book/05-distributed-git/sections/maintaining.asc index c377bb68d..0fa69d552 100644 --- a/book/05-distributed-git/sections/maintaining.asc +++ b/book/05-distributed-git/sections/maintaining.asc @@ -364,7 +364,7 @@ When a topic branch has finally been merged into `master`, it's removed from the The Git project also has a `maint` branch that is forked off from the last release to provide backported patches in case a maintenance release is required. Thus, when you clone the Git repository, you have four branches that you can check out to evaluate the project in different stages of development, depending on how cutting edge you want to be or how you want to contribute; and the maintainer has a structured workflow to help them vet new contributions. The Git project's workflow is specialized. -To clearly understand this you could check out the https://github.com/git/git/blob/master/Documentation/howto/maintain-git.txt[Git Maintainer's guide^]. +To clearly understand this you could check out the https://github.com/git/git/blob/master/Documentation/howto/maintain-git.adoc[Git Maintainer's guide^]. [[_rebase_cherry_pick]] ===== Rebasing and Cherry-Picking Workflows