Hendrik Sattler

@dscho: Sorry for the inconvenience. I though that the full discussion in the other bug report might be valuable. Thanks for extending the description.

@shiftkey How do I use TRACERX_TRACE with git-lfs? An `export TRACERX_TRACE=d:/test/tracerx.txt` or `export TRACERX_TRACE=1` does not give anything when running `git lfs clone http://server/username/repository.git`.

Same as in the git-for-windows bug report, then: trace git-lfs: tq: sending batch of size 78 trace git-lfs: api: batch 78 files trace git-lfs: HTTP: POST https://xxxxx/yyyyy/zzzzz.git/info/lfs/objects/batch > POST /yyyyy/zzzzz.git/info/lfs/objects/batch...

@dscho Thanks a lot for your detailed analysis. I will try your suggestion once I am back in the office. Might be some days, though.

Without http.sslcainfo set, it also works here. So git lfs does not really have a problem as it can easily switch between the two certificate stores/files. After all, selecting a...

@whoisj: It actually is a Git for Windows bug to have http.sslcainfo set when it is not used as shown by this bug report. If that is not considered bad,...

The build fails for me mainly because the directory that contains qmake.exe of my selected qt version is not in the PATH. OTOH, it should NOT be in the path....

BTW: don't use nmake on Windows -> only compiles with 1 CPU! GNU make is also unreliable on Windows (randomly fails to work). Ninja build tool seems to be the...

And something wrong with the cmake files because during building the solution, some files already pop up in "C:\Program Files\GammaRay" (I've built it for Qt 5.9 64-bit). That's actually a...

@krf: Everything produced by the multilib sub-build. That's due to **not** using an intermediate install directory for that sub-build but ${CMAKE_INSTALL_PREFIX}. You should use a local directory and an additional...