On Mon, Dec 14, 2009 at 07:55, Johan Herland <johan@xxxxxxxxxxx> wrote: > On Monday 14 December 2009, Richard Rossel wrote: >> Hi, >> I have a question related to the output of git gc logs. Let me >> explain, >> >> [...] >> >> I realized that the message are sent to standard error, >> so the question is why is the reason to do that? >> >> The quick solution to my problem of annoying mails is send the output >> error to /dev/null >> but what happens when an error really occur, there will be no message >> to alert me. > > Try the --quiet parameter to "git gc" (and other git commands). > > > ...Johan > > -- > Johan Herland, <johan@xxxxxxxxxxx> > www.herland.net I think the real problem that Richard is experiencing is that git fetch isn't respecting the --quiet option. The output being similar to git gc, and also being on STDERR seems to be a red-herring. Richard, What version of git are you using? Also, what is the output from 'git fetch --q; echo $?' if you just run that in your repo? If the last line you see is '0', then that should be the only output you see. -Jacob -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html