Allow to configure advisory deadlines

If a deadline is configured as advisory, the request is not aborted if
the deadline is exceeded but only a log is written. This is useful to
test how many requests would be affected by a new deadline
configuration.

Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Id3ce3e4873ce4ae6f81b7bd5845f33cc1e943c34

Documentation/config-gerrit.txt

diff --git a/Documentation/config-gerrit.txt b/Documentation/config-gerrit.txt
index 80bb0831..0cd4d62 100644
--- a/Documentation/config-gerrit.txt
+++ b/Documentation/config-gerrit.txt
@@ -5334,6 +5334,15 @@
 +
 By default, unset.
 
+[[deadline.id.isAdvisory]]deadline.<id>.isAdvisory::
++
+Whether this deadline is an advisory deadline. Advisory deadlines do not cause
+requests to be aborted when they are exceeded. Instead, if an advisory deadline
+is exceeded, only a log is written. This is useful to test how many requests
+would be affected by a new deadline configuration.
++
+By default, `false`.
+
 [[deadline.id.requestType]]deadline.<id>.requestType::
 +
 Type of request to which the deadline applies (can be `GIT_RECEIVE`, `REST` and