Re: What's cooking in git.git (Nov 2019, #03; Tue, 19)

[Derrick Stolee <stolee@gmail.com>]

On 11/19/2019 10:02 PM, Junio C Hamano wrote:
> SZEDER Gábor <szeder.dev@gmail.com> writes:
> 
>> On Tue, Nov 19, 2019 at 04:05:48PM +0900, Junio C Hamano wrote:
>>> * ds/commit-graph-delay-gen-progress (2019-11-07) 1 commit
>>>   (merged to 'next' on 2019-11-19 at afa7c921be)
>>>  + commit-graph: use start_delayed_progress()
>>
>> This commit is incomplete:
> 
> Ah, this is also just 2/2 of a two-patch pair; I guess I was extra
> sloppy on that day.
> 
> It seems that 1/2 was also incomplete, so let me discard this and
> expect both of them to resurface later.
> 
>>> * ds/sparse-cone (2019-10-23) 17 commits
>>>   (merged to 'next' on 2019-11-19 at 1eb4b3a012)
>>>  + sparse-checkout: cone mode should not interact with .gitignore
>>>  + sparse-checkout: write using lockfile
>>>  + sparse-checkout: update working directory in-process
>>>  + sparse-checkout: sanitize for nested folders
>>>  + read-tree: show progress by default
>>
>> This commit changed the default behaviour of a plumbing command, and
>> the resulting discussion concluded that such a change is not
>> desirable:
> 
> OK.  I had an impression that it was something relatively easily
> patched to restore the plumbing behaviour without taking the
> remainder of the series with a follow-on work.  If it is not the
> case, perhaps I should revert the merge to 'next' and kick it back
> to 'pu'.
> 
> Thanks for stopping me.

That commit can be ejected from the series without affecting the
correctness of any of the other commits. That will require reverting
the merge at this point, though.
Thanks,
-Stolee