Quote:
Originally Posted by nevcairiel
Did you construct that URL yourself? Because I don't see it anywhere on the GitLab page.
When you select the Clone button there, it'll give you a valid URL: https://code.videolan.org/videolan/x264.git - which works just fine with "git clone". The git protocol is being deprecated all over the web because its insecure and unscalable, in favor of HTTPS. |
HTTPS+git has never worked for me on Windows...
In this case specifically:
Code:
$ git clone https://code.videolan.org/videolan/x264.git
Cloning into 'x264'...
fatal: unable to access 'https://code.videolan.org/videolan/x264.git/': error setting certificate verify locations:
CAfile: R:/MAKE6T4/usr/lib/ssl/certs/ca-bundle.crt
CApath: none
OTOH, the git protocol has always worked with the old URL, git.videolan.org/x264.git
EDIT 1:
Okay, I found a workaround, and now git finally 1) "understands" HTTPS and 2) found the damn certificate because I created the directory where the stupid application expected to find it.
</CASE_CLOSED>
EDIT 2:
So far Mercurial has never shown the limitations that git shows on Windows... Until 2 days ago, I had always used git with
cmd.exe and in this way it only works with the git protocol... whereas Mercurial has always worked fine on the so-called command-prompt of Windows.