git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Apr 2021, #05; Mon, 19)

From
JHJeff Hostetler <git@jeffhostetler.com>
Date
Apr 20, 2021, 14:28 UTC
Message-ID
<e4bae5e3-48c2-d982-ca78-7f3ed4002a37@jeffhostetler.com>
In-Reply-To
<xmqqtuo17t6t.fsf@gitster.g>
On 4/19/21 7:25 PM, Junio C Hamano wrote:
Show 31 quoted lines
> 
> * jh/rfc-builtin-fsmonitor (2021-04-08) 23 commits
>   - t7527: test status with untracked-cache and fsmonitor--daemon
>   - p7519: add fsmonitor--daemon
>   - t7527: create test for fsmonitor--daemon
>   - fsmonitor: force update index when fsmonitor token advances
>   - fsmonitor--daemon: use a cookie file to sync with file system
>   - fsmonitor--daemon:: introduce client delay for testing
>   - fsmonitor--daemon: periodically truncate list of modified 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--daemon: implement daemon command options
>   - fsmonitor-fs-listen-macos: stub in backend for MacOS
>   - fsmonitor-fs-listen-win32: stub in backend for Windows
>   - fsmonitor--daemon: implement client command options
>   - fsmonitor--daemon: add a built-in fsmonitor daemon
>   - fsmonitor: introduce `core.useBuiltinFSMonitor` to call the daemon via IPC
>   - config: FSMonitor is repository-specific
>   - fsmonitor-ipc: create client routines for git-fsmonitor--daemon
>   - Merge branch 'jh/simple-ipc' into jh/rfc-builtin-fsmonitor
> 
>   An attempt to write and ship with a watchman equivalent tailored
>   for our use.
> 
>   Will discard.
>   ... as nobody seems to be interested.
I'd like to ask that we give this a little more time.

Is there something I could do to make it easier to review or more interesting to the community?

I hesitant to spam the list with a non-RFC/V2 until this one has seen at least a little high-level review.

Thanks Jeff

Previous: Jeff King
Message 10 of 10 in “What's cooking in git.git (Apr 2021, #05; Mon, 19)”
  1. Junio C HamanoApr 19, 2021
  2. Matheus Tavares BernardinoApr 20, 2021
  3. Ævar Arnfjörð BjarmasonApr 20, 2021
  4. Junio C HamanoApr 20, 2021
  5. brian m. carlsonApr 20, 2021
  6. Ævar Arnfjörð BjarmasonApr 21, 2021
  7. brian m. carlsonApr 21, 2021
  8. Junio C HamanoApr 20, 2021
  9. Jeff KingApr 23, 2021
  10. Jeff HostetlerApr 20, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.