trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mlib...@apache.org
Subject [17/20] trafficserver git commit: fix broken link
Date Thu, 22 Jan 2015 23:23:48 GMT
fix broken link


Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/34f36088
Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/34f36088
Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/34f36088

Branch: refs/heads/master
Commit: 34f360889409755569d6f022812aead4da5e2d86
Parents: 9df83b8
Author: Miles Libbey <mlibbey@apache.org>
Authored: Fri Jan 16 16:15:48 2015 -0800
Committer: Miles Libbey <mlibbey@apache.org>
Committed: Thu Jan 22 15:22:30 2015 -0800

----------------------------------------------------------------------
 .../accessing-the-transaction-being-processed.en.rst             | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/trafficserver/blob/34f36088/doc/sdk/header-based-plugin-examples/blacklist-plugin/accessing-the-transaction-being-processed.en.rst
----------------------------------------------------------------------
diff --git a/doc/sdk/header-based-plugin-examples/blacklist-plugin/accessing-the-transaction-being-processed.en.rst
b/doc/sdk/header-based-plugin-examples/blacklist-plugin/accessing-the-transaction-being-processed.en.rst
index 75feed1..fd2cc4d 100644
--- a/doc/sdk/header-based-plugin-examples/blacklist-plugin/accessing-the-transaction-being-processed.en.rst
+++ b/doc/sdk/header-based-plugin-examples/blacklist-plugin/accessing-the-transaction-being-processed.en.rst
@@ -27,8 +27,8 @@ In general, the return value of the handler function is not used. The
 continuation argument is the continuation being called back, the event
 is the event being sent to the continuation, and the data pointed to by
 ``void *edata`` depends on the type of event. The data types for each
-event type are listed in `Writing Handler
-Functions <../../continuations/writing-handler-functions>`__
+event type are listed in :doc:`Writing Handler
+Functions <../../continuations/writing-handler-functions.en>`
 
 The key here is that if the event is an HTTP transaction event, then the
 data passed to the continuation's handler is of type ``TSHttpTxn`` (a


Mime
View raw message