Re: What's cooking in git.git (Dec 2016, #05; Mon, 19)

On 12/27/2016 06:16 PM, Junio C Hamano wrote: > Michael Haggerty writes: > >> Sorry I didn't notice this earlier, but the `LOCK_REPORT_ON_ERROR` >> constant introduced by >> >> 3f061bf "lockfile: LOCK_REPORT_ON_ERROR", 2016-12-07 >> >> sets that constant to the value

Re: What's cooking in git.git (Dec 2016, #05; Mon, 19)

Michael Haggerty writes: > Sorry I didn't notice this earlier, but the `LOCK_REPORT_ON_ERROR` > constant introduced by > > 3f061bf "lockfile: LOCK_REPORT_ON_ERROR", 2016-12-07 > > sets that constant to the value 2,... Sorry I didn't notice this earlier, either. Thanks

Re: What's cooking in git.git (Dec 2016, #05; Mon, 19)

On 12/20/2016 01:21 AM, 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 branches, but I am still

What's cooking in git.git (Dec 2016, #05; Mon, 19)

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. The second (rather large) batch