From: Junio C Hamano <gitster@pobox.com>
To: Ben Peart <benpeart@microsoft.com>, Alex Vandiver <alexmv@dropbox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2017, #05; Fri, 17)
Date: Fri, 17 Nov 2017 15:35:01 +0900 [thread overview]
Message-ID: <xmqq375ds99m.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqbmk1sabs.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Fri, 17 Nov 2017 15:12:07 +0900")
Junio C Hamano <gitster@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.
next prev parent reply other threads:[~2017-11-17 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 6:12 What's cooking in git.git (Nov 2017, #05; Fri, 17) Junio C Hamano
2017-11-17 6:35 ` Junio C Hamano [this message]
2017-11-20 13:49 ` Ben Peart
2017-11-21 0:21 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq375ds99m.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=alexmv@dropbox.com \
--cc=benpeart@microsoft.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.