public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Richard Rossel <rrossel@inf•utfsm.cl>
To: git@vger•kernel.org
Subject: Re: git gc logs to standard error
Date: Mon, 14 Dec 2009 13:23:54 -0300	[thread overview]
Message-ID: <4B26669A.8020806@inf.utfsm.cl> (raw)
In-Reply-To: <8c9a060912140804t409030b4g168014bd80a0b88c@mail.gmail.com>

>
> On Mon, Dec 14, 2009 at 07:55, Johan Herland<johan@herland•net>  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@herland•net>
>> 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

  reply	other threads:[~2009-12-14 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 14:45 git gc logs to standard error Richard Rossel
2009-12-14 15:55 ` Johan Herland
2009-12-14 16:04   ` Jacob Helwig
2009-12-14 16:23     ` Richard Rossel [this message]
2009-12-14 16:28       ` Jacob Helwig
2009-12-14 16:37         ` Richard Rossel
2009-12-14 16:46           ` Jacob Helwig
2009-12-14 16:10   ` Richard Rossel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B26669A.8020806@inf.utfsm.cl \
    --to=rrossel@inf$(echo .)utfsm.cl \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox