Re: What's cooking in git.git (Apr 2016, #06; Thu, 21)

> >> * jk/push-client-deadlock-fix (2016-04-20) 5 commits
> [...]
> Thanks.  Something like this, perhaps?
> 
>   "git push" from a corrupt repository that attempts to push a large
>   number of refs deadlocked; the thread to relay rejection notices
>   for these ref updates blocked on writing them to the main thread,
>   after the main thread at the receiving end notices that the push
>   failed and decides not to read these notices and return a failure.

> >> * da/user-useconfigonly (2016-04-01) 2 commits
> [...]
> What often happens is that I start waiting, and then when
> necessary actions to move things forward is never taken, and there
> are many other topics that need my attention to move forward, I stop
> caring, especially when the topic is not something other people care
> about (if the original author does not care deeply enough, why
> should we?).
> 
> Let me read it over again as it has been a while and then move it
> forward with your Reviewed-by's.