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 (Mar 2022, #06; Mon, 28)
Date: Tue, 29 Mar 2022 09:58:07 -0400 [thread overview]
Message-ID: <66518eaa-efc8-b6ad-d919-abcf76ab46d9@jeffhostetler.com> (raw)
In-Reply-To: <xmqqo81pxzt4.fsf@gitster.g>
On 3/28/22 10:22 PM, Junio C Hamano wrote:
[...]
>
> * jh/builtin-fsmonitor-part2 (2022-03-25) 30 commits
> - t7527: test status with untracked-cache and fsmonitor--daemon
> - fsmonitor: force update index after large responses
> - fsmonitor--daemon: use a cookie file to sync with file system
> - fsmonitor--daemon: periodically truncate list of modified files
> - t/perf/p7519: add fsmonitor--daemon test cases
> - t/perf/p7519: speed up test on Windows
> - t/perf/p7519: fix coding style
> - t/helper/test-chmtime: skip directories on Windows
> - t/perf: avoid copying builtin fsmonitor files into test repo
> - t7527: create test for fsmonitor--daemon
> - t/helper/fsmonitor-client: create IPC client to talk to FSMonitor Daemon
> - help: include fsmonitor--daemon feature flag in version info
> - fsmonitor--daemon: implement handle_client callback
> - compat/fsmonitor/fsm-listen-darwin: implement FSEvent listener on MacOS
> - compat/fsmonitor/fsm-listen-darwin: add MacOS header files for FSEvent
> - compat/fsmonitor/fsm-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--daemon: implement 'start' command
> - fsmonitor--daemon: implement 'run' command
> - compat/fsmonitor/fsm-listen-darwin: stub in backend for Darwin
> - compat/fsmonitor/fsm-listen-win32: stub in backend for Windows
> - fsmonitor--daemon: implement 'stop' and 'status' commands
> - fsmonitor--daemon: add a built-in fsmonitor daemon
> - fsmonitor: document builtin fsmonitor
> - fsmonitor: use IPC to query the builtin FSMonitor daemon
> - fsmonitor: config settings are repository-specific
> - fsmonitor-ipc: create client routines for git-fsmonitor--daemon
> - fsmonitor: enhance existing comments, clarify trivial response handling
> (this branch is used by jh/builtin-fsmonitor-part3.)
>
> Built-in fsmonitor (part 2).
>
> Will merge to 'next'?
> source: <pull.1041.v9.git.1648231393.gitgitgadget@gmail.com>
>
I think we're good to go. Part 2 now includes all of the
fixups that we discussed over the last few weeks and I haven't
seen any further feedback.
Thanks,
Jeff
next prev parent reply other threads:[~2022-03-29 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 2:22 What's cooking in git.git (Mar 2022, #06; Mon, 28) Junio C Hamano
2022-03-29 13:58 ` Jeff Hostetler [this message]
2022-03-29 13:59 ` fr/vimdiff-layout (was: What's cooking in git.git (Mar 2022, #06; Mon, 28)) Ævar Arnfjörð Bjarmason
2022-03-29 22:51 ` What's cooking in git.git (Mar 2022, #06; Mon, 28) Neeraj Singh
2022-03-29 23:08 ` 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=66518eaa-efc8-b6ad-d919-abcf76ab46d9@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).