Re: What's cooking in git.git (Mar 2018, #01; Thu, 1)

On Fri, Mar 2, 2018 at 6:11 PM, Junio C Hamano wrote: > OK, I think I now understand what happened. I misread the "fold" > discussion and thought we were still exploring the possibility, to > avoid showing uninteresting zero-status case to the users. > > If we do not care

Re: What's cooking in git.git (Mar 2018, #01; Thu, 1)

> On 02 Mar 2018, at 18:11, Junio C Hamano wrote: > > Junio C Hamano writes: > >> SZEDER Gábor writes: >> >>> On Thu, Mar 1, 2018 at 11:20 PM, Junio C Hamano wrote: >>> *

Re: What's cooking in git.git (Mar 2018, #01; Thu, 1)

Junio C Hamano writes: > SZEDER Gábor writes: > >> On Thu, Mar 1, 2018 at 11:20 PM, Junio C Hamano wrote: >> >>> * sg/travis-build-during-script-phase (2018-01-08) 1 commit >>> - travis-ci: build Git during the 'script' phase >>> >>>

Re: What's cooking in git.git (Mar 2018, #01; Thu, 1)

SZEDER Gábor writes: > On Thu, Mar 1, 2018 at 11:20 PM, Junio C Hamano wrote: > >> * sg/travis-build-during-script-phase (2018-01-08) 1 commit >> - travis-ci: build Git during the 'script' phase >> >> Stalled for too long without any response; will

Re: What's cooking in git.git (Mar 2018, #01; Thu, 1)

On Thu, Mar 1, 2018 at 11:20 PM, Junio C Hamano wrote: > * sg/travis-build-during-script-phase (2018-01-08) 1 commit > - travis-ci: build Git during the 'script' phase > > Stalled for too long without any response; will discard. I still think this is a good change as-is and

Re: What's cooking in git.git (Mar 2018, #01; Thu, 1)

On 3/1/2018 5:20 PM, Junio C Hamano wrote: -- [Graduated to "master"] * jt/binsearch-with-fanout (2018-02-15) 2 commits (merged to 'next' on 2018-02-15 at 7648891022) + packfile: refactor hash search with fanout table + packfile: remove

Re: What's cooking in git.git (Mar 2018, #01; Thu, 1)

On 1 March 2018 at 22:20, Junio C Hamano wrote: > Here are the topics that have been cooking. Commits prefixed with > '-' are only in 'pu' (proposed updates) while commits prefixed with > '+' are in 'next'. The ones marked with '.' do not appear in any of > the integration

What's cooking in git.git (Mar 2018, #01; Thu, 1)

Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'. The ones marked with '.' do not appear in any of the integration branches, but I am still holding onto them. You can find the changes