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 (May 2022, #04; Thu, 12)
Date: Fri, 13 May 2022 15:43:17 -0400 [thread overview]
Message-ID: <455b0ce0-0e28-d3fd-c47c-38ae32d84987@jeffhostetler.com> (raw)
In-Reply-To: <xmqqilqacmmd.fsf@gitster.g>
On 5/12/22 8:16 PM, Junio C Hamano wrote:
>
> * jh/builtin-fsmonitor-part3 (2022-04-22) 29 commits
> - fsmonitor--daemon: allow --super-prefix argument
> - t7527: test Unicode NFC/NFD handling on MacOS
> - t/lib-unicode-nfc-nfd: helper prereqs for testing unicode nfc/nfd
> - fsmonitor: on macOS also emit NFC spelling for NFD pathname
> - t7527: test FSMonitor on case insensitive+preserving file system
> - fsmonitor: never set CE_FSMONITOR_VALID on submodules
> - t/perf/p7527: add perf test for builtin FSMonitor
> - t7527: FSMonitor tests for directory moves
> - fsmonitor: optimize processing of directory events
> - fsm-listen-darwin: shutdown daemon if worktree root is moved/renamed
> - fsm-health-win32: force shutdown daemon if worktree root moves
> - fsm-health-win32: add polling framework to monitor daemon health
> - fsmonitor--daemon: stub in health thread
> - fsmonitor--daemon: rename listener thread related variables
> - fsmonitor--daemon: prepare for adding health thread
> - fsmonitor--daemon: cd out of worktree root
> - fsm-listen-darwin: ignore FSEvents caused by xattr changes on macOS
> - unpack-trees: initialize fsmonitor_has_run_once in o->result
> - fsmonitor-settings: NTFS and FAT32 on MacOS are incompatible
> - fsmonitor-settings: remote repos on Windows are incompatible
> - fsmonitor-settings: remote repos on macOS are incompatible
> - fsmonitor-settings: stub in macOS-specific incompatibility checking
> - fsmonitor-settings: VFS for Git virtual repos are incompatible
> - fsmonitor-settings: stub in Win32-specific incompatibility checking
> - fsmonitor-settings: bare repos are incompatible with FSMonitor
> - t/helper/fsmonitor-client: create stress test
> - t7527: test FSMonitor on repos with Unicode root paths
> - fsm-listen-win32: handle shortnames
> - Merge branch 'jh/builtin-fsmonitor-part2' into jh/builtin-fsmonitor-part3
>
> More fsmonitor--daemon.
>
> Expecting a hopefully final reroll.
> cf. <nycvar.QRO.7.76.6.2205121726260.352@tvgsbejvaqbjf.bet>
> source: <pull.1143.v6.git.1650662994.gitgitgadget@gmail.com>
Yes, Johannes had some comments on my V6 on Thursday.
I'll address them and send a (hopefully final) V7 early
next week.
Thanks for your patience.
Jeff
prev parent reply other threads:[~2022-05-13 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 0:16 What's cooking in git.git (May 2022, #04; Thu, 12) Junio C Hamano
2022-05-13 12:06 ` js/scalar-diagnose, was " Johannes Schindelin
2022-05-13 15:34 ` Junio C Hamano
2022-05-13 19:43 ` Jeff Hostetler [this message]
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=455b0ce0-0e28-d3fd-c47c-38ae32d84987@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).