From: "Michal Suchánek" <msuchanek@suse.de>
To: git@vger.kernel.org
Subject: -q option for git to suppress informational messages?
Date: Thu, 12 Oct 2023 20:53:08 +0200 [thread overview]
Message-ID: <20231012185308.GB6241@kitsune.suse.cz> (raw)
Hello,
when using git in scripts I find that many git commands insist on
printing informational messages, and the only way to avoid this is to
sent the output to /dev/null.
While some select commands support the -q option to suppres
informational messages many don't.
Since there was recenly some discussion of problems that newcomers could
work on I suppose this could be added to the list if not there already.
Thanks
Michal
next reply other threads:[~2023-10-12 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 18:53 Michal Suchánek [this message]
2023-10-12 20:46 ` -q option for git to suppress informational messages? Emily Shaffer
2023-10-13 6:49 ` Michal Suchánek
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=20231012185308.GB6241@kitsune.suse.cz \
--to=msuchanek@suse.de \
--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