Add git versions to other parts of the spec

specification/application_service_api.rst

@@ -15,6 +15,13 @@ irrespective of the underlying homeserver implementation.
 .. contents:: Table of Contents
 .. sectnum::
 
+Specification version
+---------------------
+
+This version of the specification is generated from
+`matrix-doc <https://github.com/matrix-org/matrix-doc>`_ as of Git commit
+`{{git_version}} <https://github.com/matrix-org/matrix-doc/tree/{{git_rev}}>`_.
+
 Application Services
 --------------------
 Application services are passive and can only observe events from a given
@@ -320,4 +327,3 @@ include an ``external_url`` field in their content to provide a way for Matrix
 clients to link into the 'native' client from which the event originated.
 For instance, this could contain the message-ID for emails/nntp posts, or a link
 to a blog comment when bridging blog comment traffic in & out of Matrix.
-

specification/identity_service_api.rst

@@ -12,6 +12,13 @@ practice has only been applied specifically to email addresses.
 .. contents:: Table of Contents
 .. sectnum::
 
+Specification version
+---------------------
+
+This version of the specification is generated from
+`matrix-doc <https://github.com/matrix-org/matrix-doc>`_ as of Git commit
+`{{git_version}} <https://github.com/matrix-org/matrix-doc/tree/{{git_rev}}>`_.
+
 General principles
 ------------------
 

specification/push_gateway.rst

@@ -3,9 +3,23 @@ Push Gateway API
 
 Clients may want to receive push notifications when events are received at
 the homeserver. This is managed by a distinct entity called the Push Gateway.
-A client's homeserver forwards information about the event to the push gateway
-and the gateway submits a push notification to the push notification provider
-(e.g. APNS, GCM).
+
+.. contents:: Table of Contents
+.. sectnum::
+
+Specification version
+---------------------
+
+This version of the specification is generated from
+`matrix-doc <https://github.com/matrix-org/matrix-doc>`_ as of Git commit
+`{{git_version}} <https://github.com/matrix-org/matrix-doc/tree/{{git_rev}}>`_.
+
+Overview
+--------
+
+A client's homeserver forwards information about received events to the push
+gateway. The gateway then submits a push notification to the push notification
+provider (e.g. APNS, GCM).
 
 
 ::

specification/server_server_api.rst

@@ -44,6 +44,13 @@ request.
 .. contents:: Table of Contents
 .. sectnum::
 
+Specification version
+---------------------
+
+This version of the specification is generated from
+`matrix-doc <https://github.com/matrix-org/matrix-doc>`_ as of Git commit
+`{{git_version}} <https://github.com/matrix-org/matrix-doc/tree/{{git_rev}}>`_.
+
 Server Discovery
 ----------------
 
@@ -953,4 +960,3 @@ The list of join candidates is a list of server names that are likely to hold
 the given room; these are servers that the requesting server may wish to use as
 resident servers as part of the remote join handshake. This list may or may not
 include the server answering the query.
-