From 084adb601f2d375395c6cdcedf8af91f1065fe4e Mon Sep 17 00:00:00 2001
From: Rob Austein <sra@hactrn.net>
Date: Mon, 9 Oct 2006 16:22:20 +0000
Subject: Feh, wrong vendor branch merge proceedure, clean up before trying
 again.

svn path=/openssl/vendor/0.9.8d; revision=374
---
 openssl/vendor/0.9.8d/doc/ssl/SSL_pending.pod | 43 ---------------------------
 1 file changed, 43 deletions(-)
 delete mode 100644 openssl/vendor/0.9.8d/doc/ssl/SSL_pending.pod

(limited to 'openssl/vendor/0.9.8d/doc/ssl/SSL_pending.pod')

diff --git a/openssl/vendor/0.9.8d/doc/ssl/SSL_pending.pod b/openssl/vendor/0.9.8d/doc/ssl/SSL_pending.pod
deleted file mode 100644
index 43f2874e..00000000
--- a/openssl/vendor/0.9.8d/doc/ssl/SSL_pending.pod
+++ /dev/null
@@ -1,43 +0,0 @@
-=pod
-
-=head1 NAME
-
-SSL_pending - obtain number of readable bytes buffered in an SSL object
-
-=head1 SYNOPSIS
-
- #include <openssl/ssl.h>
-
- int SSL_pending(const SSL *ssl);
-
-=head1 DESCRIPTION
-
-SSL_pending() returns the number of bytes which are available inside
-B<ssl> for immediate read.
-
-=head1 NOTES
-
-Data are received in blocks from the peer. Therefore data can be buffered
-inside B<ssl> and are ready for immediate retrieval with
-L<SSL_read(3)|SSL_read(3)>.
-
-=head1 RETURN VALUES
-
-The number of bytes pending is returned.
-
-=head1 BUGS
-
-SSL_pending() takes into account only bytes from the TLS/SSL record
-that is currently being processed (if any).  If the B<SSL> object's
-I<read_ahead> flag is set, additional protocol bytes may have been
-read containing more TLS/SSL records; these are ignored by
-SSL_pending().
-
-Up to OpenSSL 0.9.6, SSL_pending() does not check if the record type
-of pending data is application data.
-
-=head1 SEE ALSO
-
-L<SSL_read(3)|SSL_read(3)>, L<ssl(3)|ssl(3)>
-
-=cut
-- 
cgit v1.2.3