Put a link back to the index in every page footer

Signed-off-by: Shawn O. Pearce <sop@google.com>
2009-05-28 15:55:01 -07:00 · 2009-05-28 15:55:01 -07:00 · 5500e69075
commit 5500e69075
parent 4016a930c5
23 changed files with 94 additions and 0 deletions
--- a/Documentation/access-control.txt
+++ b/Documentation/access-control.txt
@ -509,3 +509,7 @@ making any database changes to approval categories.  Category data
 is aggressively cached by every corner of Gerrit, as it does not
 change often.  Browser may need more than 5 minutes to flush the
 old category data out of their local disk caches.
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/asciidoc.conf
+++ b/Documentation/asciidoc.conf
@ -5,3 +5,14 @@ caret=&#94;
 startsb=&#91;
 endsb=&#93;
 tilde=&#126;
+
+[specialsections]
+GERRIT=gerrituplink
+
+[gerrituplink]
+<hr style="
+  height: 2px;
+  color: silver;
+  margin-top: 1.2em;
+  margin-bottom: 0.5em;
+">
--- a/Documentation/cmd-flush-caches.txt
+++ b/Documentation/cmd-flush-caches.txt
@ -83,3 +83,7 @@ SEE ALSO
 * link:cmd-show-caches.html[gerrit show-caches]
 * link:config-gerrit.html#section_cache[Cache Configuration]
 * link:config-gerrit.html#cache_names[Standard Caches]
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/cmd-index.txt
+++ b/Documentation/cmd-index.txt
@ -46,3 +46,7 @@ link:cmd-show-queue.html[gerrit show-queue]::

 link:cmd-replicate.html[gerrit replicate]::
 	Manually trigger replication, to recover a node.
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/cmd-ls-projects.txt
+++ b/Documentation/cmd-ls-projects.txt
@ -49,3 +49,7 @@ SEE ALSO
 --------

 * link:access-control.html[Access Controls]
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/cmd-replicate.txt
+++ b/Documentation/cmd-replicate.txt
@ -95,3 +95,7 @@ SEE ALSO
 --------

 * link:config-replication.html[Git Replication/Mirroring]
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/cmd-show-caches.txt
+++ b/Documentation/cmd-show-caches.txt
@ -72,3 +72,7 @@ SEE ALSO
 * link:cmd-flush-caches.html[gerrit flush-caches]
 * link:config-gerrit.html#section_cache[Cache Configuration]
 * link:config-gerrit.html#cache_names[Standard Caches]
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/cmd-show-connections.txt
+++ b/Documentation/cmd-show-connections.txt
@ -82,3 +82,7 @@ Without reverse DNS lookup:
 	
 	--
 ====
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/cmd-show-queue.txt
+++ b/Documentation/cmd-show-queue.txt
@ -73,3 +73,7 @@ DEFECTS
 There is a small race condition where tasks may disappear from the
 output of this command while they transition from the ready/waiting
 (`W`) or sleeping (`S`) state to the running (`R`) state.
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/config-contact.txt
+++ b/Documentation/config-contact.txt
@ -205,3 +205,6 @@ Free form text, as entered by the user.  The format here can be
 anything, and as the example shows, may not even be consistent in
 the same record.

+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/config-gerrit.txt
+++ b/Documentation/config-gerrit.txt
@ -498,3 +498,6 @@ This is initialized by Gerrit to be the "Registered Users" group.
 +
 Changing it is not recommended.

+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/config-gitweb.txt
+++ b/Documentation/config-gitweb.txt
@ -47,3 +47,7 @@ Caching Gitweb
 If your repository set is large and you are expecting a lot
 of users, you may want to look at the caching forks used by
 high-traffic sites like kernel.org or repo.or.cz.
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/config-headerfooter.txt
+++ b/Documentation/config-headerfooter.txt
@ -130,3 +130,6 @@ page.  Because GWT loads the module asynchronously any `<script>`
 block in the header or footer will execute before Gerrit has defined
 the function and is ready to register the hook callback.

+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/config-replication.txt
+++ b/Documentation/config-replication.txt
@ -174,3 +174,7 @@ Host keys for any destination SSH servers must appear in the user's
 `~/.ssh/known_hosts` file, and must be added in advance, before
 Gerrit starts.  If a host key is not listed, Gerrit will be unable to
 connect to that destination, and replication to that URL will fail.
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/config-sso.txt
+++ b/Documentation/config-sso.txt
@ -205,3 +205,6 @@ The user string obtained from Siteminder (e.g. the value in the
 `external_id` field.  For example, if a Siteminder username was "foo"
 then the external_id field would be populated with "gerrit:foo".

+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/dev-design.txt
+++ b/Documentation/dev-design.txt
@ -657,3 +657,7 @@ complex as Android.  Most contributors at least need some sort of
 dashboard to keep track of any pending reviews, and some way to
 correlate updated revisions back to the comments written on prior
 revisions of the same logical change.
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/dev-eclipse.txt
+++ b/Documentation/dev-eclipse.txt
@ -123,3 +123,7 @@ create SSH keys with `ssh-keygen`.

 * link:install.html[Installation Guide]
 * link:project-setup.html[Project Setup]
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/dev-readme.txt
+++ b/Documentation/dev-readme.txt
@ -152,3 +152,7 @@ Why GWT?
 We like it.  Plus we can write Java code once and run it both in
 the browser and on the server side.  This will be very useful as
 we implement offline support in Gerrit.
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/i18n-readme.txt
+++ b/Documentation/i18n-readme.txt
@ -28,3 +28,7 @@ langauges and different users want different translations.
 * The title of the host page is not translated.

 * The <noscript> tag is not translated.
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/install.txt
+++ b/Documentation/install.txt
@ -457,3 +457,7 @@ Project Setup

 See link:project-setup.html[Project Setup] for further details on
 how to register a project with Gerrit.
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/licenses.txt
+++ b/Documentation/licenses.txt
@ -576,3 +576,6 @@ All trademarks and registered trademarks mentioned herein are the
 property of their respective owners.
 ----

+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/project-setup.txt
+++ b/Documentation/project-setup.txt
@ -130,3 +130,7 @@ will automatically have `refs/heads/` prefixed to ensure they are
 a standard Git branch name.  Almost any valid SHA-1 expression can
 be used to specify the starting revision, so long as it resolves
 to a commit object.  Abbreviated SHA-1s are not supported.
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]
--- a/Documentation/user-upload.txt
+++ b/Documentation/user-upload.txt
@ -317,3 +317,7 @@ agreement is required, but not completed, it aborts the network
 connection before data is sent.  This ensures that project owners
 can be certain any object available in their repository has been
 supplied under at least one valid agreement.
+
+GERRIT
+------
+Part of link:index.html[Gerrit Code Review]