From: Tao Klerks <tao@klerks.biz>
To: git <git@vger.kernel.org>
Subject: New built-in fsmonitor: messages accidentally on stdout?
Date: Fri, 24 Sep 2021 20:02:48 +0200 [thread overview]
Message-ID: <CAPMMpoj-oiD1yDHx6WS_1uiPOXMLj7FcfBPZm-q4vO30kpE_ow@mail.gmail.com> (raw)
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 reply other threads:[~2021-09-24 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 18:02 Tao Klerks [this message]
2021-09-27 9:32 ` New built-in fsmonitor: messages accidentally on stdout? Tao Klerks
2021-09-27 13:52 ` Jeff Hostetler
2021-10-05 8:43 ` Johannes Schindelin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPMMpoj-oiD1yDHx6WS_1uiPOXMLj7FcfBPZm-q4vO30kpE_ow@mail.gmail.com \
--to=tao@klerks.biz \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).