From: Anatoly Borodin <anatoly.borodin@gmail.com>
To: git@vger.kernel.org
Subject: Re: [wishlist] disable boring messages
Date: Sat, 17 Sep 2016 16:03:07 +0000 (UTC) [thread overview]
Message-ID: <nrjpfr$565$1@blaine.gmane.org> (raw)
In-Reply-To: 20160916221753.pvqdwb7vspkosyxu@shurick.grid.su
Hi!
Alexander Inyukhin <shurick@sectorb.msk.ru> wrote:
> I have a lot of repos and a batch script to update them all,
> and I want to get rid of 'Fetching origin' and 'Already up-to-date.'
> messages leaving only new refs and tags.
There is an option `-q`, but it's too silent :)
As far as I can see, `git fetch` prints 'Fetching origin' etc to stdout,
and new refs/tags to stderr (don't ask me why). So
git fetch blabla > /dev/null
should probably do the job.
Now, if you collect and save those logs, you may need some shell-fu to
redirect that stderr to stdout, but not to /dev/null. Something like
(git fetch blabla > /dev/null) 2>&1
(run `git fetch` in a subshell)...
--
Mit freundlichen Grüßen,
Anatoly Borodin
prev parent reply other threads:[~2016-09-17 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 22:17 [wishlist] disable boring messages Alexander Inyukhin
2016-09-17 16:03 ` Anatoly Borodin [this message]
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='nrjpfr$565$1@blaine.gmane.org' \
--to=anatoly.borodin@gmail.com \
--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).