[master] 200e3dd Removing the TODO on VMOD objects documentation

Dridi Boukelmoune dridi.boukelmoune at gmail.com
Thu Sep 24 08:43:12 CEST 2015

commit 200e3dd6c3cc5175ec792033265fcbf6d36c6ff0
Author: Dridi Boukelmoune <dridi.boukelmoune at gmail.com>
Date:   Thu Sep 24 08:06:35 2015 +0200

    Removing the TODO on VMOD objects documentation
    Until I get a burst of inspiration, let's not release a blatant TODO in
    the  docs.

diff --git a/doc/sphinx/reference/vmod.rst b/doc/sphinx/reference/vmod.rst
index b3ccefa..697fc6a 100644
--- a/doc/sphinx/reference/vmod.rst
+++ b/doc/sphinx/reference/vmod.rst
@@ -382,12 +382,7 @@ first with a ``VCL_EVENT_WARM`` event, and then a ``VCL_EVENT_USE`` event.
 Unless a user decides that a given VCL should always be warm, an inactive VMOD
 will eventually become cold and should manage resources accordingly.
-.. _ref-vmod-objects:
-VMOD Objects
+.. TODO vmod objects
 When to lock, and when not to lock

More information about the varnish-commit mailing list