# [wishlist] disable boring messages 2 messages from 2016-09-16 to 2016-09-17. Participants: Alexander Inyukhin, Anatoly Borodin. Thread: https://gitlist.dev/t/44100 ## Alexander Inyukhin, 2016-09-16 22:17 Subject: [wishlist] disable boring messages Message-ID: <20160916221753.pvqdwb7vspkosyxu@shurick.grid.su> URL: https://gitlist.dev/e/20160916221753.pvqdwb7vspkosyxu%40shurick.grid.su ``` 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. ``` ## Anatoly Borodin, 2016-09-17 16:03 Subject: Re: [wishlist] disable boring messages Message-ID: URL: https://gitlist.dev/e/nrjpfr%24565%241%40blaine.gmane.org In-Reply-To: <20160916221753.pvqdwb7vspkosyxu@shurick.grid.su> ``` Hi! Alexander Inyukhin 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 ```