From: Jeff Hostetler <git@jeffhostetler.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2021, #04; Mon, 19)
Date: Tue, 20 Jul 2021 11:43:59 -0400 [thread overview]
Message-ID: <57342460-e85d-17c2-f882-373d03f63cd1@jeffhostetler.com> (raw)
In-Reply-To: <xmqq4kcqko6g.fsf@gitster.g>
On 7/19/21 5:07 PM, Junio C Hamano wrote:
>
> * jh/builtin-fsmonitor (2021-07-12) 35 commits
> - BANDAID: sparse fixes
> - t7527: test FS event reporing on MacOS WRT case and Unicode
> - fsmonitor: handle shortname for .git
> - t7527: test status with untracked-cache and fsmonitor--daemon
> - fsmonitor: force update index after large responses
> - fsmonitor: enhance existing comments
> - fsmonitor--daemon: use a cookie file to sync with file system
> - fsmonitor--daemon: periodically truncate list of modified files
> - t7527: create test for fsmonitor--daemon
> - t/perf/p7519: add fsmonitor--daemon test cases
> - t/perf: avoid copying builtin fsmonitor files into test repo
> - t/perf/p7519: speed up test using "test-tool touch"
> - t/helper/test-touch: add helper to touch a series of files
> - fsmonitor--daemon: implement handle_client callback
> - fsmonitor-fs-listen-macos: implement FSEvent listener on MacOS
> - fsmonitor-fs-listen-macos: add macos header files for FSEvent
> - fsmonitor-fs-listen-win32: implement FSMonitor backend on Windows
> - fsmonitor--daemon: create token-based changed path cache
> - fsmonitor--daemon: define token-ids
> - fsmonitor--daemon: add pathname classification
> - fsmonitor: do not try to operate on bare repos
> - fsmonitor--daemon: implement 'start' command
> - fsmonitor--daemon: implement 'run' command
> - fsmonitor-fs-listen-macos: stub in backend for MacOS
> - fsmonitor-fs-listen-win32: stub in backend for Windows
> - t/helper/fsmonitor-client: create IPC client to talk to FSMonitor Daemon
> - fsmonitor--daemon: implement 'stop' and 'status' commands
> - fsmonitor--daemon: add a built-in fsmonitor daemon
> - fsmonitor: use IPC to query the builtin FSMonitor daemon
> - fsmonitor: config settings are repository-specific
> - help: include fsmonitor--daemon feature flag in version info
> - fsmonitor-ipc: create client routines for git-fsmonitor--daemon
> - fsmonitor--daemon: update fsmonitor documentation
> - fsmonitor--daemon: man page
> - simple-ipc: preparations for supporting binary messages.
>
> An attempt to write and ship with a watchman equivalent tailored
> for our use.
>
> So, where are we with this topic?
I'm responding to comments on my V3 version and from dogfooders
of our downstream experimental releases. Hoping to submit a V4
next week.
Jeff
next prev parent reply other threads:[~2021-07-20 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 21:07 What's cooking in git.git (Jul 2021, #04; Mon, 19) Junio C Hamano
2021-07-20 1:52 ` Elijah Newren
2021-07-20 13:36 ` Derrick Stolee
2021-07-20 15:43 ` Jeff Hostetler [this message]
2021-07-21 1:11 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57342460-e85d-17c2-f882-373d03f63cd1@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).