- Jun 21, 2010
-
-
Daniel Stenberg authored
It passes the git log output through 'log2changes.pl' to produce the lot.
-
Daniel Stenberg authored
-
Daniel Stenberg authored
CHANGES is no longer used for manually edited content. It is to be generated automatically by maketgz when we make release tarballs.
-
Daniel Stenberg authored
--decorate=full is needed with my git 1.7.1 to get the necessary output so that the previous edit would work to extract the Version stuff. ... but I had to edit how the refs/tags was extracted since it had a little flaw that made it miss the 7.20.1 output. Finally, I changed so that Version is outputted even more similar to how CHANGES does it.
-
Dan Fandrich authored
Add the ASCII art header, and list version commits by decoding the ref tag names, when available (using the git log --decorate option).
-
- Jun 19, 2010
-
-
Daniel Stenberg authored
$ git log --pretty=fuller --no-color --date=short | ./log2changes.pl Of course, limiting the log output with a range like with "[tag]..HEAD" appended can be very useful too.
-
- Jun 18, 2010
-
-
Daniel Stenberg authored
For example the libssh2 based functions return other negative values than -1 to signal errors and it is important that we catch them properly. Right before this, various failures from libssh2 were treated as negative download amounts which caused havoc.
-
Daniel Stenberg authored
My additional call to Curl_pgrsUpdate() would sometimes get called even though there's no connection (left) so a NULL pointer would get passed, causing a segfault.
-
Daniel Stenberg authored
Reported-by: Steven M. Schweda
-
- Jun 17, 2010
-
-
Dan Fandrich authored
-
Kamil Dudka authored
-
Krister Johansen authored
-
Daniel Stenberg authored
1) no need to call the progress function twice when in the CURLM_STATE_TOOFAST state. 2) Make sure that the progress callback's return code is acknowledged when used
-
Daniel Stenberg authored
As long as no error is reported, the progress function can get called. This may be a little TOO often so we should keep an eye on this and possibly make this conditional somehow.
-
Daniel Stenberg authored
Previously we only accepted the option when named --disable-threaded-resover, which wasn't quite intended. Reported by: Helwing Lutz
-
- Jun 16, 2010
-
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
- Jun 10, 2010
- Jun 09, 2010
-
-
Patrick Monnerat authored
-
Yang Tse authored
-
Yang Tse authored
-
- Jun 08, 2010
-
-
Yang Tse authored
-
Yang Tse authored
-
Daniel Stenberg authored
-
Yang Tse authored
-
Yang Tse authored
-
Daniel Stenberg authored
There is an implicit conversion from "unsigned long" to "long"; rounding, sign extension, or loss of accuracy may result. Fixed by an added typecast.
-
Daniel Stenberg authored
Curl_fillreadbuffer()'s second argument takes an int, so typecasting to another is a bad idea.
-
Daniel Stenberg authored
Older unixes want an 'int' instead of 'size_t' as the 3rd argumment so before this change it would cause warnings such as: There is an implicit conversion from "unsigned long" to "int"; rounding, sign extension, or loss of accuracy may result.
-
- Jun 07, 2010
-
-
Dan Fandrich authored
Signed-off-by: Diego Casorran <dcasorran@gmail.com>
-
Yang Tse authored
-
- Jun 05, 2010
-
-
Constantine Sapuntzakis authored
Was seeing spurious SSL connection aborts using libcurl and OpenSSL. I tracked it down to uncleared error state on the OpenSSL error stack - patch attached deals with that. Rough idea of problem: Code that uses libcurl calls some library that uses OpenSSL but don't clear the OpenSSL error stack after an error. ssluse.c calls SSL_read which eventually gets an EWOULDBLOCK from the OS. Returns -1 to indicate an error ssluse.c calls SSL_get_error. First thing, SSL_get_error calls ERR_get_error to check the OpenSSL error stack, finds an old error and returns SSL_ERROR_SSL instead of SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE. ssluse.c returns an error and aborts the connection Solution: Clear the openssl error stack before calling SSL_* operation if we're going to call SSL_get_error afterwards. Notes: This is much more likely to happen with multi because it's easier to intersperse other calls to the OpenSSL library in the same thread.
-
Yang Tse authored
-
- Jun 04, 2010
-
-
Frank Meier authored
-
Daniel Stenberg authored
-
Yang Tse authored
Enable OpenLDAP support for cygwin builds. This support was disabled back in 2008 due to incompatibilities between OpenSSL and OpenLDAP headers. cygwin's OpenSSL 0.9.8l and OpenLDAP 2.3.43 versions on cygwin 1.5.25 allow building an OpenLDAP enabled libcurl supporting back to Windows 95. Remove non-functional CURL_LDAP_HYBRID code and references.
-