New built-in fsmonitor: messages accidentally on stdout?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux