curl -E: allow to escape ':' in cert nickname
curl.1: document escape sequences recognized by -E
tool_getparam: describe what parse_cert_parameter() does

... and de-duplicate the code initializing *passphrase
tool_getparam: fix memleak in handling the -E option
tool_getparam: ensure string termination in parse_cert_parameter()
src/Makefile.am: build static lib for unit tests if enabled
unit1394.c: basis of a unit test for parse_cert_parameter()
unit1394.c: plug the curl tool unit test in
build: fixed unit1394 for debug and metlink builds
runtests.pl: support nonewline="yes" in client/stdin sections
tests: Added new SMTP tests to verify commit 99b40451836d
servercert: allow empty subject

Bug: http://curl.haxx.se/bug/view.cgi?id=1220
Patch by: John Gardiner Myers
libtest: gitignore more binary files
nss: give PR_INTERVAL_NO_WAIT instead of -1 to PR_Recv/PR_Send

Reported by: David Strauss
Bug: http://curl.haxx.se/mail/lib-2013-05/0088.html
OS X framework: fix invalid symbolic link
Updated zlib version in build files.
RELEASE-NOTES: synced with ae26ee3489588f0
Revert "WIN32 MemoryTracking: track wcsdup() _wcsdup() and _tcsdup() usage"

This reverts commit 8ec2cb5544b86306b702484ea785b6b9596562ab.

We don't have any code anywhere in libcurl (or the curl tool) that use
wcsdup so there's no such memory use to track. It seems to cause mild
problems with the Borland compiler though that we may avoid by reverting
this change again.

Bug: http://curl.haxx.se/mail/lib-2013-05/0070.html
axtls: prevent memleaks on SSL handshake failures
cookies: only consider full path matches

I found a bug which cURL sends cookies to the path not to aim at.
For example:
- cURL sends a request to http://example.fake/hoge/
- server returns cookie which with path=/hoge;
  the point is there is NOT the '/' end of path string.
- cURL sends a request to http://example.fake/hogege/ with the cookie.

The reason for this old "feature" is because that behavior is what is
described in the original netscape cookie spec:
http://curl.haxx.se/rfc/cookie_spec.html

The current cookie spec (RFC6265) clarifies the situation:
http://tools.ietf.org/html/rfc6265#section-5.2.4