From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Rossel Subject: Re: git gc logs to standard error Date: Mon, 14 Dec 2009 13:23:54 -0300 Message-ID: <4B26669A.8020806@inf.utfsm.cl> References: <4B264F7B.8070504@inf.utfsm.cl> <200912141655.01268.johan@herland.net> <8c9a060912140804t409030b4g168014bd80a0b88c@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit To: git@vger.kernel.org X-From: git-owner@vger.kernel.org Mon Dec 14 17:25:35 2009 Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.50) id 1NKDiU-0005fL-P4 for gcvg-git-2@lo.gmane.org; Mon, 14 Dec 2009 17:24:11 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757769AbZLNQYB (ORCPT ); Mon, 14 Dec 2009 11:24:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757768AbZLNQYA (ORCPT ); Mon, 14 Dec 2009 11:24:00 -0500 Received: from alegre.inf.utfsm.cl ([204.87.169.3]:52088 "EHLO alegre.inf.utfsm.cl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757762AbZLNQYA (ORCPT ); Mon, 14 Dec 2009 11:24:00 -0500 Received: from trompe.intra.wiseocean.cl (red-corfo.tecnoera.net [200.24.238.226] (may be forged)) (authenticated bits=0) by alegre.inf.utfsm.cl (8.13.8/8.13.8) with ESMTP id nBEGNsG4007650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 14 Dec 2009 13:23:54 -0300 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 In-Reply-To: <8c9a060912140804t409030b4g168014bd80a0b88c@mail.gmail.com> X-Virus-Scanned: ClamAV 0.94.2/10165/Mon Dec 14 12:47:56 2009 on alegre.inf.utfsm.cl X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on alegre.inf.utfsm.cl Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: > > On Mon, Dec 14, 2009 at 07:55, Johan Herland 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, >> 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 > $ git --version git version 1.5.4.3 And when there is no change in the repo $ git fetch --q; echo $? 0 no messages and no error , but when there is a change to syncronize $ git fetch --q; echo $? remote: Counting objects: 7, done. remote: Compressing objects: 100% (5/5), done. remote: Total 5 (delta remote: 2), reused 0 (delta 0) Unpacking objects: 100% (5/5), done. From git@boss:sandbox 3e4df7f..b92d27c master -> origin/master 0 here come the messages but the return value is still 0 I will try to update git to v1.6.5.6 and see what happend -- Richard Rossel Airsage Inc. Valparaiso - Chile