summary refs log tree commit diff
diff options
context:
space:
mode:
authorBrendan Abolivier <babolivier@matrix.org>2020-01-07 15:15:16 +0000
committerBrendan Abolivier <babolivier@matrix.org>2020-01-07 15:15:16 +0000
commit3675fb9bc6b0f9fd068bee443c1499042359ee99 (patch)
tree567e42d71c5870e2e8e782c1dbcd09e4060e7077
parentIncorporate review (diff)
downloadsynapse-3675fb9bc6b0f9fd068bee443c1499042359ee99.tar.xz
Fix reference
-rw-r--r--docs/message_retention_policies.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/message_retention_policies.md b/docs/message_retention_policies.md
index 42b637516f..c4888c81be 100644
--- a/docs/message_retention_policies.md
+++ b/docs/message_retention_policies.md
@@ -83,7 +83,7 @@ expired events from the database. They are only run if support for
 message retention policies is enabled in the server's configuration. If
 no configuration for purge jobs is configured by the server admin,
 Synapse will use a default configuration, which is described in the
-[sample configuration file](https://github.com/matrix-org/synapse/blob/v1.7.3/docs/sample_config.yaml#L332-L393).
+[sample configuration file](https://github.com/matrix-org/synapse/blob/master/docs/sample_config.yaml#L332-L393).
 
 Some server admins might want a finer control on when events are removed
 depending on an event's room's policy. This can be done by setting the