Documentation: make AsciiDoc links always point to HTML files
AsciiDoc's "link" is supposed to create hyperlinks for HTML output, so prefer a "link" to point to an HTML file instead of a text file if an HTML version of the file is being generated. For RelNotes, keep pointing to text files as no equivalent HTML files are generated. If appropriate, also update the link description to not contain the linked file's extension. Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Sebastian Schuberth committed
Sep 6, 2013 at 22:03 UTC
d5ff3b4be5b2e3eee9c4b298f00ed7a4c1c556a4
7 files changed
+10
-10
Documentation/everyday.txt
+1
-1
@@ -304,7 +304,7 @@ and maintain access to the repository by developers.
304
* linkgit:git-shell[1] can be used as a 'restricted login shell'
305
for shared central repository users.
306
307
-link:howto/update-hook-example.txt[update hook howto] has a good
307
+link:howto/update-hook-example.html[update hook howto] has a good
308
example of managing a shared central repository.
309
310
Documentation/git-credential.txt
+1
-1
@@ -20,7 +20,7 @@ usernames and passwords. The git-credential command exposes this
20
interface to scripts which may want to retrieve, store, or prompt for
21
credentials in the same manner as Git. The design of this scriptable
22
interface models the internal C API; see
23
-link:technical/api-credentials.txt[the Git credential API] for more
23
+link:technical/api-credentials.html[the Git credential API] for more
24
background on the concepts.
25
26
git-credential takes an "action" option on the command-line (one of
Documentation/git-rebase.txt
+2
-2
@@ -322,7 +322,7 @@ You may find this (or --no-ff with an interactive rebase) helpful after
322
reverting a topic branch merge, as this option recreates the topic branch with
323
fresh commits so it can be remerged successfully without needing to "revert
324
the reversion" (see the
325
-link:howto/revert-a-faulty-merge.txt[revert-a-faulty-merge How-To] for details).
325
+link:howto/revert-a-faulty-merge.html[revert-a-faulty-merge How-To] for details).
326
327
--ignore-whitespace::
328
--whitespace=<option>::
@@ -416,7 +416,7 @@ Without --interactive, this is a synonym for --force-rebase.
416
You may find this helpful after reverting a topic branch merge, as this option
417
recreates the topic branch with fresh commits so it can be remerged
418
successfully without needing to "revert the reversion" (see the
419
-link:howto/revert-a-faulty-merge.txt[revert-a-faulty-merge How-To] for details).
419
+link:howto/revert-a-faulty-merge.html[revert-a-faulty-merge How-To] for details).
420
421
include::merge-strategies.txt[]
422
Documentation/git-revert.txt
+1
-1
@@ -59,7 +59,7 @@ brought in by the merge. As a result, later merges will only bring in tree
59
changes introduced by commits that are not ancestors of the previously
60
reverted merge. This may or may not be what you want.
61
+
62
-See the link:howto/revert-a-faulty-merge.txt[revert-a-faulty-merge How-To] for
62
+See the link:howto/revert-a-faulty-merge.html[revert-a-faulty-merge How-To] for
63
more details.
64
65
--no-edit::
Documentation/gitcvs-migration.txt
+1
-1
@@ -157,7 +157,7 @@ points. You can use these, for example, to send all commits to the shared
157
repository to a mailing list. See linkgit:githooks[5].
158
159
You can enforce finer grained permissions using update hooks. See
160
-link:howto/update-hook-example.txt[Controlling access to branches using
160
+link:howto/update-hook-example.html[Controlling access to branches using
161
update hooks].
162
163
Providing CVS Access to a Git Repository
Documentation/technical/http-protocol.txt
+2
-2
@@ -499,5 +499,5 @@ References
499
500
link:http://www.ietf.org/rfc/rfc1738.txt[RFC 1738: Uniform Resource Locators (URL)]
501
link:http://www.ietf.org/rfc/rfc2616.txt[RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1]
502
-link:technical/pack-protocol.txt
503
-link:technical/protocol-capabilities.txt
502
+link:technical/pack-protocol.html
503
+link:technical/protocol-capabilities.html
Documentation/user-manual.txt
+2
-2
@@ -1977,7 +1977,7 @@ $ git clone http://yourserver.com/~you/proj.git
1977
-------------------------------------------------
1978
1979
(See also
1980
-link:howto/setup-git-server-over-http.txt[setup-git-server-over-http]
1980
+link:howto/setup-git-server-over-http.html[setup-git-server-over-http]
1981
for a slightly more sophisticated setup using WebDAV which also
1982
allows pushing over HTTP.)
1983
@@ -3191,7 +3191,7 @@ those "loose" objects.
3191
You can save space and make Git faster by moving these loose objects in
3192
to a "pack file", which stores a group of objects in an efficient
3193
compressed format; the details of how pack files are formatted can be
3194
-found in link:technical/pack-format.txt[technical/pack-format.txt].
3194
+found in link:technical/pack-format.html[pack format].
3195
3196
To put the loose objects into a pack, just run git repack:
3197