git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [wishlist] disable boring messages

From
Anatoly Borodin <anatoly.borodin@gmail.com>
Date
Sep 17, 2016, 16:03 UTC
Message-ID
<nrjpfr$565$1@blaine.gmane.org>
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
Previous: Alexander Inyukhin
Message 2 of 2 in “[wishlist] disable boring messages”
  1. Alexander InyukhinSep 16, 2016
  2. Anatoly BorodinSep 17, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.