Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Maintenance backports for v23 #3409

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Sep 3, 2015
Merged

Maintenance backports for v23 #3409

merged 10 commits into from
Sep 3, 2015

Conversation

carlosmn
Copy link
Member

@carlosmn carlosmn commented Sep 3, 2015

Nothing ground-breaking, but a few nice fixes have accumulated over the last month. I did not include the one which changes what we return for a bad pkt length as that's a string change, but it might be convenient enough for finding out what the server sent that I could be convinced to include it.

slavikus and others added 9 commits September 3, 2015 11:09
OS X may have libssh2 in diff locations, so CHECK_LIBRARY_EXISTS may check the wrong lib; forcing it to use a found directory.
When curl uses a proxy, it will only use Basic unless we prompt it to
try to use the most secure on it has available.

This is something which git did recently, and it seems like a good idea.
When we're looking to update a tag, we can't stop if the tag auto-follow
rules don't say to update it. The tag might still match the refspec we
were given.
The conditional checked cbs->transfer_progress then used the value in cbs->push_transfer_progress. In both cases it should be push_transfer_progress
When we ask for credentials, the user may choose to return EUSER to
indicate that an error has happened on its end and it wants to be given
back control.

We must therefore pass that back to the user instead of mentioning that
it was on_headers_complete() that returned an error code. Since we can,
we return the exact error code from the user (other than PASSTHROUGH)
since it doesn't cost anything, though using other error codes aren't
recommended.
When parsing user-provided regex patterns for functions, we must not
fail to provide a diff just because a pattern is not well
formed. Ignore it instead.
Starting at OS X 10.8, the Security framework offers some functions
which are unified across OS X and iOS. These are the functions that we
use.

Older versions of OS X do not have these functions and we fail to
compile. In these situations, fall back to using OpenSSL for our TLS
stream instead.
Include the copyright notice from the deps/winhttp/ sources.  Move the
LGPL to the bottom of the file (since multiple dependencies are LGPL
licensed) and include the actual copyright notices from the regex sources.
@ethomson
Copy link
Member

ethomson commented Sep 3, 2015

Awesome! Thanks for your diligence with maintenance releases.

ethomson added a commit that referenced this pull request Sep 3, 2015
Maintenance backports for v23
@ethomson ethomson merged commit c712203 into maint/v0.23 Sep 3, 2015
@carlosmn carlosmn deleted the update-v23 branch December 9, 2015 02:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants