> -----Original Message-----
> From: Junio C Hamano [mailto:gits...@pobox.com]
> Sent: Friday, November 17, 2017 1:35 AM
> To: Ben Peart <ben.pe...@microsoft.com>; Alex Vandiver
> <ale...@dropbox.com>
> Cc: git@vger.kernel.org
> Subject: Re: What's cooking in git.git (Nov 2017, #05; Fri, 17)
> 
> Junio C Hamano <gits...@pobox.com> writes:
> 
> > * av/fsmonitor (2017-11-13) 7 commits
> >   (merged to 'next' on 2017-11-13 at db56ad7eef)  + fsmonitor:
> > simplify determining the git worktree under Windows  ...
> >
> >  Various fixes to bp/fsmonitor topic.
> >
> >  Waiting for follow-on fixes to settle.
> >
> >
> > * bp/fsmonitor (2017-10-05) 15 commits
> >   (merged to 'next' on 2017-11-07 at b08d44ba60)  + fsmonitor:
> > preserve utf8 filenames in fsmonitor-watchman log  ...
> >
> >  Originally merged to 'next' on 2017-10-05
> >
> >  We learned to talk to watchman to speed up "git status" and other
> > operations that need to see which paths have been modified.
> >
> >  Waiting for follow-on fixes to settle.
> 
> 
> The two topics were waiting for updates to av/fsmonitor to quiet down,
> which seem to have happened by now, so I'll consider merging them to
> 'master' soonish.
> 
> Please let me know if I should wait for a bit longer.
> 
> Thanks.

As far as I can tell, the patches are good.  I'm not aware of anything else 
that should hold it up.

I had the one question about the way the test was written but that was nothing 
that should hold up the patch - just my own curiosity.

Reply via email to