From: Ben Peart <peartben@gmail.com>
Date: Mon, 30 Oct 2017 12:40:36 GMT
Subject: Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)
Message-ID: <aa7b33a8-4110-39e4-f722-f87f6b0a8ea5@gmail.com>
In-Reply-To: <xmqqr2tl40pl.fsf@gitster.mtv.corp.google.com>

> 
> * av/fsmonitor (2017-10-30) 5 commits
>   - SQUASH???
>   - fsmonitor: delay updating state until after split index is merged
>   - fsmonitor: document GIT_TRACE_FSMONITOR
>   - fsmonitor: don't bother pretty-printing JSON from watchman
>   - fsmonitor: set the PWD to the top of the working tree
>   (this branch uses bp/fsmonitor.)
> 
>   Various fixes to bp/fsmonitor topic.
> 
>   What's the status of this one?  I recall that I saw Dscho's "looks
>   good" respose to the cover letter, and Ben sounded positive on most
>   of the patches in the previous series.  Except for the SQUASH??? I
>   had to add to squelch compiler warnings, is this good to go?
> 

This looks good to go from my perspective.