From: Matt Caswell <matt@openssl.org>
Date: Sat, 5 Jul 2014 21:31:05 +0000 (+0100)
Subject: Fixed error in pod files with latest versions of pod2man
X-Git-Tag: OpenSSL_1_0_0n~38
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=cf3792b3e4e26aa826147699e32f6e8221434a59;p=oweals%2Fopenssl.git

Fixed error in pod files with latest versions of pod2man

(cherry picked from commit 07255f0a76d9d349d915e14f969b9ff2ee0d1953)
---

diff --git a/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod b/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod
index 610523407a..b9371d7697 100644
--- a/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod
+++ b/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod
@@ -74,7 +74,7 @@ further processing will occur. The following return values have meaning:
 
 =over 4
 
-=item 2
+=item Z<>2
 
 This indicates that the I<ctx> and I<hctx> have been set and the session can 
 continue on those parameters. Additionally it indicates that the session
@@ -82,12 +82,12 @@ ticket is in a renewal period and should be replaced. The OpenSSL library will
 call I<cb> again with an enc argument of 1 to set the new ticket (see RFC5077
 3.3 paragraph 2).
 
-=item 1
+=item Z<>1
 
 This indicates that the I<ctx> and I<hctx> have been set and the session can 
 continue on those parameters.
 
-=item 0
+=item Z<>0
 
 This indicates that it was not possible to set/retrieve a session ticket and 
 the SSL/TLS session will continue by by negiotationing a set of cryptographic