Re: What's cooking in git.git (May 2017, #06; Mon, 22)

Jonathan Nieder [off-list ref] writes:

Junio C Hamano wrote:

quoted

Jonathan Nieder [off-list ref] writes:

quoted

Junio C Hamano wrote:

quoted

quoted

quoted

* bw/forking-and-threading (2017-05-15) 14 commits

[...]

quoted

quoted

quoted

 The "run-command" API implementation has been made more robust
 against dead-locking in a threaded environment.

 Will merge to 'next'.

What's holding this up?  The deadlock it fixed was a real,
non-theoretical issue.

Does "Being down-sick over the weekend" count?

Yes.  Sorry, I should have asked in a more productive way.

I applied the patches locally to ensure tests continue to pass
reproducibly but was worried because the patches had been ejected from
"next" and had been in "Will merge" state for the last couple of
pushes.

There also is "which ones should go first to 'master'".  Regression
fixes want to go earlier than fixes to age-old issues, for example.

In any case, today was my "move them to 'next'" day (I aim to have
approximately 2 such days a week), so quite a few things will now be
in 'next' when today's integration cycle finishes.