Use https:// instead of git:// for cryptomilk

[mohamed]

In many companies, the git:// protocol is blocked by corporate firewall. To circumvent that, use http:// instead of git://

[mohamed]

@salasoom @lindstro BTW, I have just tested "https://" instead of "http://" and that seems to work as well. I leave it up to you guys to decide which protocol to use.

[lindstro]

@mohamed Interesting. We have the exact reverse problem at LLNL, where pushes over https are blocked, and we have to use git+ssh. But I see no particular issue with changing the protocol for cmocka.

@salasoom Do you agree?

[mohamed]

@lindstro You don't need to push over https. This is simply pulling from the cmocka repo. I hope that LLNL doesn't block read-only https access.

[lindstro]

@mohamed Right. I was merely pointing out that our default protocol is git+ssh so we can push new zfp code to GitHub. That's probably why we're not using https for pulling cmocka, but as you note, we should be able to do so without problem.

[salasoom]

We can go with https here. I will rebase the branch against develop, and amend the commit to use https.

[codecov-io]

Codecov Report

Merging #33 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #33   +/-   ##
========================================
  Coverage    92.43%   92.43%           
========================================
  Files           46       46           
  Lines         2248     2248           
========================================
  Hits          2078     2078           
  Misses         170      170

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ba1a464...96eb6b6. Read the comment docs.