<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 15, 2017, at 6:04 AM, Robert Helling <<a href="mailto:helling@atdotde.de" class="">helling@atdotde.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dirk,<div class=""><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 15. Nov 2017, at 14:44, Dirk Hohndel <<a href="mailto:dirk@hohndel.org" class="">dirk@hohndel.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Fun fact: if you push to a branch on Subsurface-divelog/subsurface (which you can, Robert), the CI will build a Windows binary for you. And even for a PR it will do that (and the log will show you where on transfer.sh the binary can be found.</span></div></blockquote></div><div class=""><br class=""></div>I followed the mailing list in as much as I am aware of that. But the patch I attached was for libgit2 (to provide more debugging information) and that as far as I understand I cannot get into our travis build. I wanted to understand what that library thinks it should take as proxy (which would then be a hint as to where look further).</div></div></div></blockquote><br class=""></div><div>My mistake. I triggered a new local build on our old infrastructure where I can easily modify libraries like this.</div><div><br class=""></div><div>Davide, can you test with this binary:</div><div><br class=""></div><div><a href="http://subsurface-divelog.org/downloads/test/subsurface-4.7.4-21-gbd9dad7371f8.exe" class="">http://subsurface-divelog.org/downloads/test/subsurface-4.7.4-21-gbd9dad7371f8.exe</a></div><div><br class=""></div><div>That will tell us what libgit thinks the proxy might be.</div><div><br class=""></div><div>With Lubomir's changes there are two ways to get the console output:</div><div><br class=""></div><div>You can run from cmd.exe - then the output is shown on the screen, but not saved to the log files.</div><div>Or you can run this by double clicking on the executable. Then the log output is saved to the two log files.</div><div><br class=""></div><div>Thanks</div><div><br class=""></div><div>/D</div><br class=""></body></html>