wording tweak for tls_init() from jsing

ok jsing, schwarze

Simplify and shorten the description of tls_init(3),
fixing an awkward wording noticed by tb@.
OK tb@

Automatically handle library initialisation for libtls.

Now that we have tls_init() under pthread_once(), automatically initialise
libtls from the entry point functions (tls_config(), tls_client() a

Automatically handle library initialisation for libtls.

Now that we have tls_init() under pthread_once(), automatically initialise
libtls from the entry point functions (tls_config(), tls_client() and
tls_server()) - this makes an explicit tls_init() call no longer a
requirement.

ok bcook@ beck@ inoguchi@

show more ...

un-revert tls_init pthread_once change, now that stub is added so that builds work

backout. diff was not tested comprehensively, resulting in a broken tree.

Make tls_init() concurrently callable using pthread_once().
ok jsing@

This brings pthread_once usage into libressl, which will
need to get dealt with correctly in portable.

This sets us up to autoi

Make tls_init() concurrently callable using pthread_once().
ok jsing@

This brings pthread_once usage into libressl, which will
need to get dealt with correctly in portable.

This sets us up to autoinit libtls, and we will also be
using pthread_once to deal with autoinit stuff in libssl
and libcrypto

show more ...

Be explicit about when it is safe to call tls_config_free().

Discussed with beck@

tls_free(3) and tls_config_free(3) accept NULL;
patch from Matthew Martin <phy1729 at gmail dot com>,
slightly tweaked by me

spelling fix;

document tls_config_error(3) RETURN VALUES, improve what is said
about tls_error(3), and warn about some traps;
OK jmc@

add HISTORY and AUTHORS

Fix Copyright notices; ok beck@ jsing@ tedu@

split the tls_init(3) that had grown fat to allow healthy future growth;
suggested by jsing@; "i would just chuck it in" jmc@