From: Junio C Hamano Date: Fri, 06 Sep 2013 21:43:34 GMT Subject: Re: [PATCH] Documentation: Make AsciiDoc links always point to HTML files Message-ID: In-Reply-To: <522A350A.5040903@gmail.com> Sebastian Schuberth writes: > 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 > --- Makes sense; we should have done this back when we applied 5e00439f (Documentation: build html for all files in technical and howto, 2012-10-23). > Documentation/everyday.txt | 2 +- > Documentation/git-credential.txt | 2 +- > Documentation/git-rebase.txt | 4 ++-- > Documentation/git-revert.txt | 2 +- > Documentation/gitcvs-migration.txt | 2 +- > Documentation/technical/http-protocol.txt | 4 ++-- > Documentation/user-manual.txt | 4 ++-- > 7 files changed, 10 insertions(+), 10 deletions(-) > > diff --git a/Documentation/everyday.txt b/Documentation/everyday.txt > index e1fba85..2a18c1f 100644 > --- a/Documentation/everyday.txt > +++ b/Documentation/everyday.txt > @@ -304,7 +304,7 @@ and maintain access to the repository by developers. > * linkgit:git-shell[1] can be used as a 'restricted login shell' > for shared central repository users. > > -link:howto/update-hook-example.txt[update hook howto] has a good > +link:howto/update-hook-example.html[update hook howto] has a good > example of managing a shared central repository. > > > diff --git a/Documentation/git-credential.txt b/Documentation/git-credential.txt > index 7da0f13..b211440 100644 > --- a/Documentation/git-credential.txt > +++ b/Documentation/git-credential.txt > @@ -20,7 +20,7 @@ usernames and passwords. The git-credential command exposes this > interface to scripts which may want to retrieve, store, or prompt for > credentials in the same manner as Git. The design of this scriptable > interface models the internal C API; see > -link:technical/api-credentials.txt[the Git credential API] for more > +link:technical/api-credentials.html[the Git credential API] for more > background on the concepts. > > git-credential takes an "action" option on the command-line (one of > diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt > index 6b2e1c8..94e07fd 100644 > --- a/Documentation/git-rebase.txt > +++ b/Documentation/git-rebase.txt > @@ -322,7 +322,7 @@ You may find this (or --no-ff with an interactive rebase) helpful after > reverting a topic branch merge, as this option recreates the topic branch with > fresh commits so it can be remerged successfully without needing to "revert > the reversion" (see the > -link:howto/revert-a-faulty-merge.txt[revert-a-faulty-merge How-To] for details). > +link:howto/revert-a-faulty-merge.html[revert-a-faulty-merge How-To] for details). > > --ignore-whitespace:: > --whitespace=