Hi Junio, On Thu, 25 Oct 2018, Junio C Hamano wrote: > "Johannes Schindelin via GitGitGadget" <gitgitgadget@xxxxxxxxx> > writes: > > > For a long time already, we have Git's source code continuously tested via > > Travis CI, see e.g. https://travis-ci.org/git/git/builds/421738884. It has > > served us well, and more and more developers actually pay attention and > > benefit from the testing this gives us. > > What's the current status of this topic? Has the "p4 daemon gets > left behind" one resolved to everybody's satisfaction? No. I was kind of waiting for Luke's answer, and in the alternative I hoped to find some time to work on trying to reproduce his issues on my system (but I failed to find said time so far). > I think that one was the only large discussion on the series (aside from > "do we want to keep Travis?" subthread, which does not make this series > undesirable), modulo your "oy oy oy that is leftover debugging I need to > remove in a reroll". > > The topic was marked as "On hold, monitoring discussion" and it > seems that discussion has quieted down, so the next step is to see > an updated series? I really think that I have to figure out what causes those p4d issues before I can give you that updated. I *am* interested, to be sure, it's just that other things seem to get in my way all the time. One thing that keeps getting in my way, for example, is the performance issue identified in the chain linter. And I do think that I have to take this into consideration for another update to this here patch series, too, by adding `--no-chain-lint` to the Windows phase. There is a similar thing with `--with-dashes`, too. Will keep you updated, Dscho > > Thanks. > > >
