From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 6BD431F9E5 for ; Tue, 20 Jul 2021 15:55:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240053AbhGTPG5 (ORCPT ); Tue, 20 Jul 2021 11:06:57 -0400 Received: from siwi.pair.com ([209.68.5.199]:26607 "EHLO siwi.pair.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242551AbhGTPDg (ORCPT ); Tue, 20 Jul 2021 11:03:36 -0400 Received: from siwi.pair.com (localhost [127.0.0.1]) by siwi.pair.com (Postfix) with ESMTP id 669363F40F4; Tue, 20 Jul 2021 11:44:01 -0400 (EDT) Received: from AZHCI-MGMT.azhci.com (162-238-212-202.lightspeed.rlghnc.sbcglobal.net [162.238.212.202]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by siwi.pair.com (Postfix) with ESMTPSA id 4A1673F40F1; Tue, 20 Jul 2021 11:44:01 -0400 (EDT) Subject: Re: What's cooking in git.git (Jul 2021, #04; Mon, 19) To: Junio C Hamano , git@vger.kernel.org References: From: Jeff Hostetler Message-ID: <57342460-e85d-17c2-f882-373d03f63cd1@jeffhostetler.com> Date: Tue, 20 Jul 2021 11:43:59 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 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