Merge branch 'PHP-7.4'

* PHP-7.4:
  Remove extension readmes

13 files changed, 0 insertions, 799 deletions

diff --git a/ext/dba/README b/ext/dba/README
deleted file mode 100644
index ec0610b71f..0000000000
--- a/ext/dba/README
+++ /dev/null
@@ -1,54 +0,0 @@
-These functions build the foundation for accessing Berkeley DB style
-databases.
-
-This is a general abstraction layer for several file-based databases. As
-such, functionality is limited to a common subset of features supported
-by modern databases such as Sleepycat Software's DB2. (This is not to be
-confused with IBM's DB2 software, which is supported through the ODBC
-functions.)
-
-This extensions allows to work with the following databases:
-dbm      DBM is the oldest (original) type of Berkeley DB style databases.
-         You should avoid it, if possible. We do not support the
-         compatibility functions built into DB2 and gdbm, because they are
-         only compatible on the source code level, but cannot handle the
-         original dbm format.
-ndbm     NDBM is a newer type and more flexible than dbm. It still has
-         most of the arbitrary limits of dbm (therefore it is deprecated).
-gdbm     GDBM is the GNU database manager.
-db2      DB2 is Sleepycat Software's DB2. It's described as "a programmatic
-         toolkit that provides high-performance built-in database support
-         for both standalone and client/server applications.
-db3      DB3 is Sleepycat Software's DB3.
-db4      DB4 is Sleepycat Software's DB4. This is available since PHP 5.0.
-cdb      CDB is "a fast, reliable, lightweight package for creating and
-         reading constant databases." It is from the author of qmail and
-         can be found at http://cr.yp.to/cdb.html. Since it is constant,
-         we support only reading operations. And since PHP 4.3.0 we support
-         writing (not updating) through the internal cdb library.
-cdb_make Since PHP 4.3.0 we support creation (not updating) of cdb files
-         when the bundled cdb library is used.
-flatfile This is available since PHP 4.3.0 for compatibility with the
-         deprecated dbm extension only and should be avoided. However you
-         may use this where files were created in this format. That happens
-         when configure could not find any external library.
-inifile  This is available since PHP 4.3.3 to be able to modify php.ini
-         files from within PHP scripts. When working with ini files you
-         can pass arrays of the form array(0=>group,1=>value_name) or
-         strings of the form "[group]value_name" where group is optional.
-         As the functions dba_firstkey() and dba_nextkey() return string
-         representations of the key there is a new function dba_key_split()
-         available since PHP 5 which allows to convert the string keys into
-         array keys without losing FALSE.
-qdbm     This is available since PHP 5.0.0. The qdbm library can be loaded
-         from http://qdbm.sourceforge.net.
-
-
-After configuring and compiling PHP you must execute the following test
-from commandline:
-  php run-tests.php ext/dba.
-This shows whether your combination of handlers works. Most problematic
-are dbm and ndbm which conflict with many installations. The reason for
-this is that on several systems these libraries are part of more than one
-other library. The configuration test only prevents you from configuring
-malfaunctioning single handlers but not combinations.
diff --git a/ext/hash/README b/ext/hash/README
deleted file mode 100644
index 8c01afa6b1..0000000000
--- a/ext/hash/README
+++ /dev/null
@@ -1,19 +0,0 @@
-Generic hashing framework for PHP
-
-Simplest usages:
-
-$digest = hash($algoname, $message);
-$digest = hash_file($algoname, $filename);
-
-Examples:
-
-$digest = hash('md5', 'The quick brown fox jumped over the lazy dog.');
-
-Feeder usage:
-
-$context = hash_init($algoname);
-hash_update($context, $message);
-$digest = hash_final($context);
-
-hash(), hash_file(), and hash_final() each support an optional boolean parameter $raw_output which behaves in the same
-manner as sha1()'s optional parameter.
diff --git a/ext/opcache/README b/ext/opcache/README
deleted file mode 100644
index 99b8c0f2c9..0000000000
--- a/ext/opcache/README
+++ /dev/null
@@ -1,215 +0,0 @@
-The Zend OPcache
-================
-
-The Zend OPcache provides faster PHP execution through opcode caching and
-optimization. It improves PHP performance by storing precompiled script
-bytecode in the shared memory. This eliminates the stages of reading code from
-the disk and compiling it on future access. In addition, it applies a few
-bytecode optimization patterns that make code execution faster.
-
-Compatibility
--------------
-
-This version of Zend OPcache is compatible with PHP 5.2.*, 5.3.*, 5.4.*
-and PHP-5.5 development branch.  PHP 5.2 support may be removed in the future.
-
-Quick Install
--------------
-
-- Compile
-
- $PHP_DIR/bin/phpize
- ./configure \
-      --with-php-config=$PHP_DIR/bin/php-config
- make
-
-- Install
-
- make install # this will copy opcache.so into PHP extension directory
-
-- Edit php.ini
-
- zend_extension=/...full path.../opcache.so
-
-NOTE: In case you are going to use Zend OPcache together with Xdebug or Zend Debugger,
-be sure that the debugger is loaded after OPcache. "php -v" must show the debugger
-after OPcache.
-
-- Restart PHP
-
-Speed Tuning
--------------
-
-We recommend the following configuration options for best performance
-in a production environment.
-
-opcache.memory_consumption=128
-opcache.interned_strings_buffer=8
-opcache.max_accelerated_files=4000
-opcache.revalidate_freq=60
-opcache.enable_cli=1
-
-You also may add the following, but it may break some applications and
-frameworks. Please, read description of these directives and add them on your
-own risk.
-
-opcache.save_comments=0
-opcache.enable_file_override=1
-
-In some cases you may like to prefer enabling/disabling some features
-to avoid incompatibilities at the cost of some performance degradation.
-
-For development environment we would recommend setting opcache.revalidate_freq
-into 0.
-
-Configuration Directives
-------------------------
-
-opcache.enable (default "1")
-	OPcache On/Off switch. When set to Off, code is not optimized and cached.
-
-opcache.enable_cli (default "0")
-	Enables the OPcache for the CLI version of PHP. It's mostly for testing
-	and debugging.
-
-opcache.memory_consumption (default "64")
-	The OPcache shared memory storage size. The amount of memory for storing
-	precompiled PHP code in Mbytes.
-
-opcache.interned_strings_buffer (default "4")
-	The amount of memory for interned strings in Mbytes.
-
-opcache.max_accelerated_files (default "2000")
-	The maximum number of keys (scripts) in the OPcache hash table.
-	The number is actually the first one in the following set of prime
-	numbers that is bigger than the one supplied: { 223, 463, 983, 1979, 3907,
-	7963, 16229, 32531, 65407, 130987, 262237, 524521, 1048793 }. Only numbers
-	between 200 and 1000000 are allowed.
-
-opcache.max_wasted_percentage (default "5")
-    When the cache fills up this setting decides when to actually reset (dump
-    all entries) it. At the default of 5% it means that if less than 5% of
-    the entries in the now full cache are wasted/orphaned, then you have a good
-    active cache. There is no point emptying a cache full of good entries
-    only to most likely refill it with those same entries. Once more than 5%
-    of the cache consists of wasted entries, the cache will reset in this
-    cache-full scenario. This can be set up to as high as 50%.
-
-opcache.use_cwd (default "1")
-	When this directive is enabled, the OPcache appends the current working
-	directory to the script key, thus eliminating possible collisions between
-	files with the same name (basename). Disabling the directive improves
-	performance, but may break existing applications.
-
-opcache.validate_timestamps (default "1")
-	When disabled, you must reset the OPcache manually or restart the
-	webserver for changes to the filesystem to take effect.
-	The frequency of the check is controlled by the directive
-	"opcache.revalidate_freq".
-
-opcache.validate_permission (default "0")
-	Leads OPcache to check file readability on each access to cached file.
-	This directive should be enabled in shared hosting environment, when few
-	users (PHP-FPM pools) reuse the common OPcache shared memory.
-
-opcache.validate_root (default "0")
-	This directive prevents file name collisions in different "chroot"
-	environments. It should be enabled for sites that may serve requests in
-	different "chroot" environments.
-
-opcache.revalidate_freq (default "2")
-	How often (in seconds) to check file timestamps for changes to the shared
-	memory storage allocation. ("1" means validate once per second, but only
-	once per request. "0" means always validate)
-
-opcache.file_update_protection (default "2")
-	Prevents caching files that are less than this number of seconds old.
-	It protects from caching of incompletely updated files. In case all file
-	updates on your site are atomic, you may increase performance setting it
-	to "0".
-
-opcache.revalidate_path (default "0")
-	Enables or disables file search in include_path optimization
-	If the file search is disabled and a cached file is found that uses
-	the same include_path, the file is not searched again. Thus, if a file
-	with the same name appears somewhere else in include_path, it
-	won't be found. Enable this directive if this optimization has an effect on
-	your applications. The default for this directive is disabled, which means
-	that optimization is active.
-
-opcache.save_comments (default "1")
-	If disabled, all PHPDoc comments are dropped from the code to reduce the
-	size of the optimized code. Disabling "Doc Comments" may break some
-	existing applications and frameworks (e.g. Doctrine, ZF2, PHPUnit)
-
-opcache.enable_file_override (default "0")
-	Allow file existence override (file_exists, etc.) performance feature.
-
-opcache.optimization_level (default "0xffffffff")
-	A bitmask, where each bit enables or disables the appropriate OPcache
-	passes
-
-opcache.dups_fix (default "0")
-	Enable this hack as a workaround for "Cannot redeclare class" errors.
-
-opcache.blacklist_filename
-	The location of the OPcache blacklist file (wildcards allowed).
-	Each OPcache blacklist file is a text file that holds the names of files
-	that should not be accelerated. The file format is to add each filename
-	to a new line. The filename may be a full path or just a file prefix
-	(i.e., /var/www/x  blacklists all the files and directories in /var/www
-	that start with 'x'). Line starting with a ; are ignored (comments).
-	Files are usually triggered by one of the following three reasons:
-	1) Directories that contain auto generated code, like Smarty or ZFW cache.
-	2) Code that does not work well when accelerated, due to some delayed
-	   compile time evaluation.
-	3) Code that triggers an OPcache bug.
-
-opcache.max_file_size (default "0")
-	Allows exclusion of large files from being cached. By default all files
-	are cached.
-
-opcache.consistency_checks (default "0")
-	Check the cache checksum each N requests.
-	The default value of "0" means that the checks are disabled.
-	Because calculating the checksum impairs performance, this directive should
-	be enabled only as part of a debugging process.
-
-opcache.force_restart_timeout (default "180")
-	How long to wait (in seconds) for a scheduled restart to begin if the cache
-	is not being accessed.
-	The OPcache uses this directive to identify a situation where there may
-	be a problem with a process. After this time period has passed, the
-	OPcache assumes that something has happened and starts killing the
-	processes that still hold the locks that are preventing a restart.
-	If the log level is 3 or above, a "killed locker" error is recorded
-	in the Apache logs when this happens.
-
-opcache.error_log
-	OPcache error_log file name. Empty string assumes "stderr".
-
-opcache.log_verbosity_level (default "1")
-	All OPcache errors go to the Web server log.
-	By default, only fatal errors (level 0) or errors (level 1) are logged.
-	You can also enable warnings (level 2), info messages (level 3) or
-	debug messages (level 4).
-
-opcache.preferred_memory_model
-	Preferred Shared Memory back-end. Leave empty and let the system decide.
-
-opcache.protect_memory (default "0")
-	Protect the shared memory from unexpected writing during script execution.
-	Useful for internal debugging only.
-
-opcache.restrict_api (default "")
-	Allows calling OPcache API functions only from PHP scripts which path is
-	started from specified string. The default "" means no restriction.
-
-opcache.mmap_base
-	Mapping base of shared memory segments (for Windows only). All the PHP
-	processes have to map shared memory into the same address space. This
-	directive allows to manually fix the "Unable to reattach to base address"
-	errors.
-
-opcache.lockfile_path (default "/tmp")
-	Absolute path used to store shared lockfiles (for *nix only)
diff --git a/ext/openssl/README b/ext/openssl/README
deleted file mode 100644
index 6241675658..0000000000
--- a/ext/openssl/README
+++ /dev/null
@@ -1,320 +0,0 @@
-OpenSSL extension for PHP
-
-The functions implemented so far make it possible to seal and open data, and
-also create and verify signatures.
-
-NEW: support for S/MIME encrypt/decrypt/sign/verify, as well as more
-flexibility for specifying certificates/keys.
-
-To enable the extension, configure PHP with --with-openssl.
-
-Specifying keys/certificates
-----------------------------
-
-Most of the functions require a key or a certificate as a parameter; to make
-things easy for you to use openssl, this extension allows you
-to specify certificates in the following way:
-
-1. As an X.509 resource returned from openssl_x509_read
-2. As a string in the format file://filename, where filename is the path to the
-   certificate file (it will be opened and read automatically)
-3. As a string containing the data from the certificate file
-
-Similarly, you can use the following methods of specifying a public key:
-
-1. As a key resource returned from openssl_get_publickey
-2. An X509 resource - public key only
-3. As a string in the format file://filename
-4. As a string containing the data from the key file
-
-Additionally, for a private key, when the openssl extension function does not
-allow you to enter the passphrase as a parameter you may use the syntax
-array($key, "passphrase") where $key can be a key specified using one of the
-methods listed above.
-
-Certificate Verification
-------------------------
-When calling a function that will verify a signature/certificate, the cainfo
-parameter is an array containing file and directory names that specifiy the
-locations of trusted CA files.  If a directory is specified, then it must be a
-correctly hashed directory.
-
-Misc:
------
-
-mixed openssl_error_string()
-
-returns the message from the last error that the OpenSSL library encountered
-and moves it's internal error pointer to the next message.  If there are no
-more error messages, returns false.
-
-General Key/Cert Functions:
----------------------------
-
-resource openssl_get_privatekey(mixed key [, string passphrase])
-
-Parses the key data and returns a key resource identifier. If the key is
-encrypted a passphrase is needed. This can be supplied as second argument.
-
-
-resource openssl_get_publickey(mixed cert)
-
-Extracts the public key from the given certificate or public key and returns
-a key resource identifier.
-
-
-void openssl_free_key(resource key)
-
-Frees the resource given by the key resource identifier.
-Note that this function does not accept the extended key specification
-syntax mentioned above, as it doesn't make sense in this case!
-
-array openssl_x509_parse(mixed x509[, bool shortnames=true])
-
-Parses the certificate data and returns an array containing information
-about the certificate, it's intended purposes, subject, issuer, validity
-etc. etc.  If shortnames is true (the default) then the fields will be
-keyed by the shortname forms eg: CN as opposed to commonName (shortnames
-= false).
-
-
-bool openssl_x509_checkpurpose(mixed x509cert, int purpose,
-	array cainfo[, string untrustedfile])
-
-Verifies if the certificate can be used for a specific purpose.
-Purpose can be one of the following values:
-	X509_PURPOSE_SSL_CLIENT
-	X509_PURPOSE_SSL_SERVER
-	X509_PURPOSE_NS_SSL_SERVER
-	X509_PURPOSE_SMIME_SIGN
-	X509_PURPOSE_SMIME_ENCRYPT
-	X509_PURPOSE_CRL_SIGN
-	X509_PURPOSE_ANY
-
-cainfo is an array of CA information (as mentioned above).
-untrusted file specifies a file containing a bunch of certs that
-are not trusted but may be useful in validating the certificate.
-
-
-resource openssl_read_x509(mixed cert)
-
-Parses the cert and returns a resource that can be used with the
-other openssl functions
-
-
-void openssl_free_x509(resource x509)
-
-Frees the resource given by the x509 resource identifier.
-Note that this function does not accept the extended cert specification
-syntax mentioned above, as it doesn't make sense in this case!
-
-
-PKCS7 (S/MIME) Sign/Verify/Encrypt/Decrypt Functions:
------------------------------------------------------
-
-These functions allow you to manipulate S/MIME messages!
-
-They are based on apps/smime.c from the openssl dist, so for information,
-see the documentation for openssl.
-
-You may pass in some flags that affect how these functions work using
-and array containing the following values:
-"detached", "nodetached", "text", "nointern", "noverify", "nochain",
-"nocerts", "noattr", "binary", "nosigs".
-The options correspond to the options of the same name for the
-"openssl smime" command (smime(1)).
-
-
-bool openssl_pkcs7_verify(string filename, array flags[, string signerscerts][,
-		array cainfo])
-
-Verifies that the signature on the MIME message contained in the file
-named by filename is valid.  If signerscerts is passed in, it holds the
-name of a file into which the certificates of those that signed the
-message will be stored.
-cainfo and flags are CA information and flag information as described
-above.
-
-
-bool openssl_pkcs7_encrypt(string infile, string outfile, array recipcerts,
-		array headers[, array flags])
-
-Encrypts the MIME message contained in the file named by infile using
-the certificates held in recipcerts.  The result is place in the file
-named outfile.
-recipcerts is an array of certificate identifiers representing the certs
-of the intended recipients of the message.
-headers is an array of headers to prepend to the message: they will
-not be included in the encoded section.
-flags is flag information as described above.
-Hint: you will want to put "To", "From", and "Subject" headers in headers.
-Headers can be either an assoc array keyed by header named, or can be
-and indexed array containing a single header line per value.
-The message will be encoded using a RC2-40 bit cipher.
-TODO: allow user to specify cipher.
-
-bool openssl_pkcs7_sign(string infile, string outfile, mixed signcert, mixed
-		signkey, array headers[, array flags][, string extracertsfilename])
-
-Signs the MIME message contained in the file named by infile using the
-certificate and key pair identified by signcert/signkey.
-Signkey must be the private key corresponding to signcert.
-The result is placed in the file named by outfile.
-Headers and flags have the same effects as mentioned above.
-extracertsfilename names a file containing a bunch of additional certificates
-to include in the signature, in order to aid the recipient in verifying the
-message.
-
-
-bool openssl_pkcs7_decrypt(string infilename, string outfilename, mixed
-		recipcert, mixed recipkey)
-
-Decrypts the MIME message contained in the file named by infilename
-using the certificate and private key pair recipcert/recipkey.
-The descrypted result is placed in outfilename.
-TODO: add flags parameter, if needed?
-
-
-EVP Sign/Verify/Encrypt/Decrypt Functions:
-------------------------------------------
-
-bool openssl_sign(string data, &string signature, mixed key)
-
-Uses key to create signature for data, returns true on success and false
-on failure. signature is passed by reference and contains the newly created
-signature on success.
-
-
-int openssl_verify(string data, string signature, mixed key)
-
-Uses key to verify that the signature is correct for the given data.
-Returns 1 if correct, 0 if incorrect, and -1 on error.
-
-
-int openssl_seal(string data, &string sealdata, &array ekeys, array pubkeys)
-
-Encrypts data using pubkeys, so that only owners of the respective private
-keys and ekeys can decrypt and read the data. Returns the length of the
-sealed data on success, else false. On success, sealdata and ekeys hold
-the sealed data and envelope keys.
-
-
-bool openssl_open(string data, &string opendata, string ekey, int privkey)
-
-Opens (decrypts) sealed data using a private key and the corresponding
-envelope key. Returns true on success and false on failure.  On success,
-opendata will hold the descypted data.
-
-
-See below for more details on usage. Also feel free to mail me at
-venaas@php.net if you have questions. The OpenSSL documentation,
-especially the EVP documentation at
-http://www.openssl.org/docs/crypto/evp.html, might also be of help.
-
-
-HOWTO:
-
-To do anything you need a private key and a certificate containing the
-corresponding public key. This is similar to what you have using say an
-Apache webserver with OpenSSL. For testing you could try keys that come
-with OpenSSL, that's what the sample scripts below do. You can also get
-keys from some CA, or you can create them yourself.
-
-
-Creating private key
-
-To generate an unprotected 1024 bit RSA private key you can do
-
-   openssl genrsa -out /tmp/test.key 1024
-
-Private keys should be protected by a passphrase though.
-
-
-Creating a self signed certificate
-
-To generate a self signed certificate from the key that is valid for
-365 days, do
-
-    openssl req -new -key /tmp/test.key -out /tmp/test.crt -days 365 -x509
-
-
-Example usage
-
-These examples use keys that come with OpenSSL, you should perhaps test with
-those first.
-
-
-Seal and open
-
-     <?php
-     $data = "Follow the white rabbit";
-
-     // Get certificate into a string
-     // this file comes with OpenSSL 0.9.6
-     $fp = fopen("/src/openssl-0.9.6/demos/maurice/cert.pem", "r");
-     $cert = fread($fp, 8192);
-     fclose($fp);
-     // get public key from certificate
-     $pk1 = openssl_get_publickey($cert);
-     // $pk1 is an encryption key resource id if success, else false
-     // Repeat if want public keys for multiple parties
-
-     $fp = fopen("/src/openssl-0.9.6/demos/sign/cert.pem", "r");
-     $cert = fread($fp, 8192);
-     fclose($fp);
-     $pk2 = openssl_get_publickey($cert);
-
-     // seal data, only owners of $pk1 and $pk2 can decrypt $sealed with keys
-     // $ekeys[0] and $ekeys[1] respectively.
-     openssl_seal($data, $sealed, $ekeys, array($pk1,$pk2));
-     openssl_free_key($pk1);
-     openssl_free_key($pk2);
-
-     // now we try to decrypt data for one of the recipients
-     $fp = fopen("/src/openssl-0.9.6/demos/sign/key.pem", "r");
-     // Get PEM coded key into $pkey
-     $pkey = fread($fp, 8192);
-     fclose($fp);
-     // $key will be resource id for unpacked $pkey
-     $key = openssl_get_privatekey($pkey);
-
-     openssl_open($sealed, $open, $ekeys[1], $key);
-     openssl_free_key($key);
-     echo "$open\n";
-     ?>
-
-
-Sign and verify
-
-     <?php
-     $data = "Follow the white rabbit";
-
-     // First we need to have a string containing the private key in PEM format
-     // this file comes with OpenSSL 0.9.6
-     $fp = fopen("/src/openssl-0.9.6/demos/sign/key.pem", "r");
-     $pkey = fread($fp, 8192);
-     fclose($fp);
-
-     // get private key from the PEM format
-     // $key is an encr key resource id if success, else false
-     $key = openssl_get_privatekey($pkey);
-
-     // calculate signature
-     openssl_sign($data, $signature, $key);
-     openssl_free_key($key);
-
-     // recipient verifies signature
-     // read certificate
-     $fp = fopen("/src/openssl-0.9.6/demos/sign/cert.pem", "r");
-     $cert = fread($fp, 8192);
-     fclose($fp);
-
-     // Get public key from the certificate
-     $pubkey = openssl_get_publickey($cert);
-
-     // state whether signature is okay or not
-     echo openssl_verify($data, $signature, $pubkey) == 1 ? "ok\n" : "bad\n";
-
-     // free key
-     openssl_free_key($pubkey);
-     ?>
diff --git a/ext/pcntl/README b/ext/pcntl/README
deleted file mode 100644
index ab1dfa1f2d..0000000000
--- a/ext/pcntl/README
+++ /dev/null
@@ -1,11 +0,0 @@
-Process Control Module for PHP (pcntl)
-
-This module will attempt to implement all features related to process spawning and
-control (fork(), waitpid(), signal(), WIF's, etc). This is extremely experimental,
-with hope to become stable on most UNIX's. I greatly apreciate any feedback, fixes,
-and or suggestions on how to improve/better implement
-this functionality.
-
-Thanks,
-
-Jason Greeme < jason@inetgurus.net / jason@php.net >
diff --git a/ext/pdo/README b/ext/pdo/README
deleted file mode 100644
index a778543822..0000000000
--- a/ext/pdo/README
+++ /dev/null
@@ -1,50 +0,0 @@
-PHP Data Objects
-================
-
-Concept: Data Access Abstraction
-
-Goals:
-
-1/  Be light-weight
-2/  Provide common API for common database operations
-3/  Be performant
-4/  Keep majority of PHP specific stuff in the PDO core (such as persistent
-    resource management); drivers should only have to worry about getting the
-    data and not about PHP internals.
-
-
-Transactions and autocommit
-===========================
-
-When you create a database handle, you *should* specify the autocommit
-behaviour that you require.  PDO will default to autocommit on.
-
-$dbh = new PDO("...", $user, $pass, array(PDO_ATTR_AUTOCOMMIT => true));
-
-When auto-commit is on, the driver will implicitly commit each query as it is
-executed.  This works fine for most simple tasks but can be significantly
-slower when you are making a large number of udpates.
-
-$dbh = new PDO("...", $user, $pass, array(PDO_ATTR_AUTOCOMMIT => false));
-
-When auto-commit is off, you must then use $dbh->beginTransaction() to
-initiate a transaction.  When your work is done, you then call $dbh->commit()
-or $dbh->rollBack() to persist or abort your changes respectively.  Not all
-databases support transactions.
-
-You can change the auto-commit mode at run-time:
-
-$dbh->setAttribute(PDO_ATTR_AUTOCOMMIT, false);
-
-Regardless of the error handling mode set on the database handle, if the
-autocommit mode cannot be changed, an exception will be thrown.
-
-Some drivers will allow you to temporarily disable autocommit if you call
-$dbh->beginTransaction().  When you commit() or rollBack() such a transaction,
-the handle will switch back to autocommit mode again.  If the mode could not
-be changed, an exception will be raised, as noted above.
-
-When the database handle is closed or destroyed (or at request end for
-persistent handles), the driver will implicitly rollBack().  It is your
-responsibility to call commit() when you are done making changes and
-autocommit is turned off.
diff --git a/ext/pdo_dblib/README b/ext/pdo_dblib/README
deleted file mode 100644
index e833c74b6a..0000000000
--- a/ext/pdo_dblib/README
+++ /dev/null
@@ -1,23 +0,0 @@
-This is the unified Sybase-DB style driver for PDO.
-
-This extension register itself as:
-	- 'mssql' when built against the Microsoft DBLIB library
-	- 'sybase' when built against Sybase ct-lib
-	- 'dblib' when built against FreeTDS
-
-The following database products are free for testing:
-	- Microsoft SQL Server Express (Windows Only)
-	- Sybase Adaptive Server (Windows, Linux, *NIX)
-	- Microsoft SQL Server Azure (One Month Trial Cloud Service)
-
-You must set the following environment variables to run the tests:
-	- PDO_DBLIB_TEST_DSN  - DSN (e.g., dblib:host=localhost;dbname=test)
-	- PDO_DBLIB_TEST_USER - database user
-	- PDO_DBLIB_TEST_PASS - database user password
-
-This extension supports multiple versions of the TDS protocol. There are
-behavioral differences between versions. When making changes, it's recommended
-to test across all supported versions. You can specify a version using a version
-parameter in the DSN. See dblib_driver.c:pdo_dblib_handle_factory() for valid
-values. Some tests check version-specific behavior by parsing this string, so
-it's best to use the DSN (rather than freetds.conf, etc.) to set the version.
diff --git a/ext/pspell/README b/ext/pspell/README
deleted file mode 100644
index 9fc884c65b..0000000000
--- a/ext/pspell/README
+++ /dev/null
@@ -1,51 +0,0 @@
-README file for pspell (spellchecker) module for PHP
-----------------------------------------------------
-
-The latest release of pspell is always available from
-
-  http://aspell.net/
-
-This module was developed and tested with aspell-.31.1 and pspell-.11.0.2,
-although slightly earlier (and hopefully later) versions of those libraries
-should work as well.
-
-General notes
--------------
-
-Please, note that somewhere around version .27.x (I believe) aspell stopped
-working with the aspell module for php. This is due to the fact that the
-author changed things around a bit, and suggested that people link to pspell
-in the future rather than to aspell. That's exactly what this module is for.
-It has the same basic functionality as aspell (and more features are being
-added). I did not want to modify existing aspell module, because it would
-break things for those who are using older aspell, or result in very ugly code.
-Rather, I wrote a new module - pspell.
-
-
-Building pspell on a Unix system
---------------------------------
-
-In order to use pspell, you need to have *both* aspell and pspell libraries
-installed, and they have to be compatible with each other. Get the latest
-release of both at the URL given above.
-
-I expect the libraries to be in /usr/local (that's the default when you
-cofigure pspell and aspell with their 'configure' scripts woth no parameters).
-If that location is different, please specify it in --with-pspell=PATH, where
-PATH is the path you specified for pspell libraries.
-
-Notes on personalized dictionaries
-----------------------------------
-
-It is now possible to have personalized dictionaries with pspell. This is
-achieved by opening a dictionary with pspell_new_personal() rather than
-pspell_new() and specifying the custom dictionary as the first parameter.
-The parameter probably should begin with '/' because otherwise it will
-be relative to $HOME, which is probably set to "/root". This is probably not
-what you want because you need write access for nobody to be able to write
-to a dictionary. Once the dictionary is open, you can use
-pspell_add_to_personal() to add words to the wordlist and finally
-pspell_save_wordlist() to save it.
-
-Note that at this moment pspell_save_wordlist() will return TRUE, even if
-there was an error. This will be changed once pspell library is fixed.
diff --git a/ext/readline/README.libedit b/ext/readline/README.libedit
deleted file mode 100644
index a19371056e..0000000000
--- a/ext/readline/README.libedit
+++ /dev/null
@@ -1,4 +0,0 @@
-This library can be built with libedit - non-GPL drop-in readline replacement.
-Libedit can be obtained from http://sourceforge.net/projects/libedit/
-It is taken from NetBSD (http://www.netbsd.org/) CVS repository and modified
-to work as stand-alone library.
diff --git a/ext/shmop/README.md b/ext/shmop/README.md
deleted file mode 100644
index b89c0d8e79..0000000000
--- a/ext/shmop/README.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Shared Memory Operations Extension to PHP
-
-While developing a search deamon we needed a php based front end to communicate
-the deamon via SHM. PHP already had a shared memory extension (sysvshm) written
-by Christian Cartus <cartus@atrior.de>, unfortunately this extension was designed
-with PHP only in mind and offers high level features which are extremely
-bothersome for basic SHM we had in mind.  After spending a day trying to reverse
-engineer and figure out the format of sysvshm we decided that it would be much
-easier to add our own extension to php for simple SHM operations, we were right :)).
diff --git a/ext/simplexml/README b/ext/simplexml/README
deleted file mode 100644
index 406b312002..0000000000
--- a/ext/simplexml/README
+++ /dev/null
@@ -1,34 +0,0 @@
-SimpleXML is meant to be an easy way to access XML data.
-
-SimpleXML objects follow four basic rules:
-
-1) properties denote element iterators
-2) numeric indices denote elements
-3) non numeric indices denote attributes
-4) string conversion allows to access TEXT data
-
-When iterating properties then the extension always iterates over
-all nodes with that element name. Thus method children() must be
-called to iterate over subnodes. But also doing the following:
-foreach ($obj->node_name as $elem) {
-  // do something with $elem
-}
-always results in iteration of 'node_name' elements. So no further
-check is needed to distinguish the number of nodes of that type.
-
-When an elements TEXT data is being accessed through a property
-then the result does not include the TEXT data of subelements.
-
-Known issues
-============
-
-Due to engine problems it is currently not possible to access
-a subelement by index 0: $object->property[0].
-
-TODO
-====
-
-At the moment property access to multiple elements of the same
-name returns an array of SimpleXML objects. This should be an
-object of a new type instead so that all kinds of linkage,
-assignment and deleting would work.
diff --git a/ext/spl/README b/ext/spl/README
deleted file mode 100644
index 39f3215bc8..0000000000
--- a/ext/spl/README
+++ /dev/null
@@ -1,4 +0,0 @@
-This is an extension that aims to implement some efficient data access
-interfaces and classes.
-
-For more information look at: http://php.net/manual/en/book.spl.php
diff --git a/ext/xmlreader/README b/ext/xmlreader/README
deleted file mode 100644
index 66f16b6cbc..0000000000
--- a/ext/xmlreader/README
+++ /dev/null
@@ -1,5 +0,0 @@
-XMLReader represents a reader that provides non-cached,
-forward-only access to XML data. It is based upon the
-xmlTextReader api from libxml
-
-This extension is designed to only work under PHP 5+.