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

New built-in fsmonitor: messages accidentally on stdout?

From
Tao Klerks <tao@klerks.biz>
Date
Sep 24, 2021, 18:02 UTC
Message-ID
<CAPMMpoj-oiD1yDHx6WS_1uiPOXMLj7FcfBPZm-q4vO30kpE_ow@mail.gmail.com>
Hi folks,

I've been testing the new "core.usebuiltinfsmonitor=true" capability in Git for Windows 2.33.0.windows.2, and came across something today that threw off my scripting:

In general, git "informational" messages are always output on stderr; this caught me out initially, but is a godsend for scripting.

However, with this new functionality, the "starting fsmonitor-daemon in 'C:/whatever" message is being output on stdout!

This interferes with scripting around things like "git status --porcelain".

I understand this fsmonitor stuff is still somewhat in-flux (patched into the windows port but not yet "regular" git releases?), and this issue may already have been reported and addressed in the latest set of patches - my apologies if that is the case!

Best regards, Tao

Next: Tao Klerks
Message 1 of 4 in “New built-in fsmonitor: messages accidentally on stdout?”
  1. Tao KlerksSep 24, 2021
  2. Tao KlerksSep 27, 2021
  3. Jeff HostetlerSep 27, 2021
  4. Johannes SchindelinOct 5, 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.