Junio C HamanoCurrently
$ git grep '\([^t]\|^\)'link: user-manual.txt
gives four hits that refer to .txt version of the documentation set, but at least "hooks" and "cvs-migration" have HTML variants installed, so refer to them instead.
Signed-off-by: Junio C Hamano <junkio@cox.net> ---
* The other two are howto/setup-git-server-over-http and technical/pack-format.txt
Documentation/user-manual.txt | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
Show changes to Documentation/user-manual.txt +2 −2
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index 13db969..a7abeaa 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -1875,7 +1875,7 @@ $ chmod a+x hooks/post-update (For an explanation of the last two lines, see gitlink:git-update-server-info[1], and the documentation -link:hooks.txt[Hooks used by git].) +link:hooks.html[Hooks used by git].) Advertise the url of proj.git. Anybody else should then be able to clone or pull from that url, for example with a commandline like: @@ -1959,7 +1959,7 @@ Setting up a shared repository Another way to collaborate is by using a model similar to that commonly used in CVS, where several developers with special rights all push to and pull from a single shared repository. See -link:cvs-migration.txt[git for CVS users] for instructions on how to +link:cvs-migration.html[git for CVS users] for instructions on how to set this up. [[setting-up-gitweb]]