Re: What's cooking in git.git (Oct 2016, #09; Mon, 31)

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 2, 2016, 12:57 UTC
Message-ID: <xmqqy412dopj.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <alpine.DEB.2.20.1611021054030.3264@virtualbox>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 13 quoted lines

> On Mon, 31 Oct 2016, Junio C Hamano wrote:
>
>> * jc/git-open-cloexec (2016-10-31) 3 commits
>>  - sha1_file: stop opening files with O_NOATIME
>>  - git_open_cloexec(): use fcntl(2) w/ FD_CLOEXEC fallback
>>  - git_open(): untangle possible NOATIME and CLOEXEC interactions
>> 
>>  The codeflow of setting NOATIME and CLOEXEC on file descriptors Git
>>  opens has been simplified.
>
> This branch (in particular, the "use fcntl(2)" one) breaks the build on
> Windows. Until this breakage is resolved, I won't be able to see (nor
> report) any test breakages in `pu`.

Thanks for a heads-up. Anything in 'pu' won't be of importance until 2.11 final, so please don't worry too much about it. Instead please do make sure the tip of 'master' is OK.

Having said that, an incremental update or replacement to help preparing it for post 2.11 final is appreciated ;-)

FYI, I may be offline for a few days.