Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Don't hard-code HTTPS cap & clarify the meanings of the features enum#4032

Merged
ethomson merged 2 commits intomasterlibgit2/libgit2:masterfrom
cmn/https-cap-no-hardcodelibgit2/libgit2:cmn/https-cap-no-hardcodeCopy head branch name to clipboard
Dec 20, 2016
Merged

Don't hard-code HTTPS cap & clarify the meanings of the features enum#4032
ethomson merged 2 commits intomasterlibgit2/libgit2:masterfrom
cmn/https-cap-no-hardcodelibgit2/libgit2:cmn/https-cap-no-hardcodeCopy head branch name to clipboard

Conversation

@carlosmn
Copy link
Member

Most importantly, clarify what we mean by HTTPS and SSH being supported.

/cc @ethomson I think this should go into the next release.

This partially reverts bdec62d which activates
the transport code-paths which allow you to use a custom TLS implementation
without having to have one at build-time.

However the capabilities describe how libgit2 was built, not what it could
potentially support, bring back the ifdefs so we only say we support HTTPS if
libgit2 was itself built with a TLS implementation.
Most importantly, clarify what it means for HTTPS and SSH to be supported.
@carlosmn carlosmn added this to the libgit2 v0.25 - Rutschgefahr milestone Dec 17, 2016
@ethomson ethomson merged commit f91f170 into master Dec 20, 2016
@ethomson ethomson deleted the cmn/https-cap-no-hardcode branch January 9, 2019 10:29
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.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.