* [wishlist] disable boring messages
@ 2016-09-16 22:17 Alexander Inyukhin
2016-09-17 16:03 ` Anatoly Borodin
0 siblings, 1 reply; 2+ messages in thread
From: Alexander Inyukhin @ 2016-09-16 22:17 UTC (permalink / raw)
To: git
Hi,
is it possible to make git silent, when nothing interesting
is happening?
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [wishlist] disable boring messages
2016-09-16 22:17 [wishlist] disable boring messages Alexander Inyukhin
@ 2016-09-17 16:03 ` Anatoly Borodin
0 siblings, 0 replies; 2+ messages in thread
From: Anatoly Borodin @ 2016-09-17 16:03 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-09-17 16:03 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-09-16 22:17 [wishlist] disable boring messages Alexander Inyukhin
2016-09-17 16:03 ` Anatoly Borodin
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).