All of lore.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:10:25 -0300	[thread overview]
Message-ID: <4B266371.9040106@inf.utfsm.cl> (raw)
In-Reply-To: <200912141655.01268.johan@herland.net>

>
> 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
>
>    


Yes,  the quiet option works when I do 'git gc', but in the cron file 
there is no
git-gc command, only fetch and reset. I suppose that  those commands 
calls (internally)
to git-gc.
Also I try with -q option in fetch and reset but without results, the 
only thing that
works was with 2>/dev/null, but as I mention before, is not a good idea 
because
I will miss the real errors messages.

The real question here is why git-gc send those logs to the standard 
error instead of
standard output?

--
Richard Rossel
Airsage Inc.
Valparaiso - Chile

      parent reply	other threads:[~2009-12-14 16:10 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
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 [this message]

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=4B266371.9040106@inf.utfsm.cl \
    --to=rrossel@inf.utfsm.cl \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.